I have installed freenx with this article
http://wiki.centos.org/HowTos/FreeNX
but when I use freenx-client on windows to connect to server,
I always get an "freenx Authentication failed."
client err log output as this:
NX> 203 NXSSH running with pid: 1584
NX> 285 Enabling check on switch command
NX> 285 Enabling skip of SSH config files
NX> 285 Setting the preferred NX options
NX> 200 Connected to address: 192.168.253.5 on port: 22
NX> 202 Authenticating user: nx
NX> 208 Using auth method: publickey
NX> 204 Authentication failed.
My sshd configed as use rsa key, and ssh soft like xshell can work well.
nxsetup output as this: Pleas care the following red commented two line. I just
think this is the point.
But why , and what shoud I do to solver ?
[root at tigertall ~]# nxsetup --test
----> Testing your nxserver configuration ...
Warning: Could not find nxdesktop in /usr/bin. RDP sessions won't work.
Warning: Could not find nxviewer in /usr/bin. VNC sessions won't work.
Warning: Invalid value
"APPLICATION_LIBRARY_PRELOAD=/usr/lib/libX11.so.6.2:/usr/lib/libXext.so.6.4:/usr/lib/libXcomp.so.2:/usr/lib/libXcompext.so:/usr/lib/libXrender.so.1.2".
/usr/lib/libX11.so.6.2 could not be found. Users will not be able to run a
single application in non-rootless mode.
Warning: Invalid value "DEFAULT_X_SESSION=/etc/X11/xdm/Xsession"
Users might not be able to request a default X session.
Warning: Invalid value "COMMAND_START_CDE=cdwm"
Users will not be able to request a CDE session.
Warning: Invalid value "COMMAND_SMBMOUNT=smbmount". You'll not be
able to use SAMBA.
Warning: Invalid value "COMMAND_SMBUMOUNT=smbumount". You'll not
be able to use SAMBA.
Error: Could not find 1.5.0 or 2.[01].0 or 3.[01].0 version string in nxagent.
NX 1.5.0 or 2.[01].0 or 3.[012].0 backend is needed for this version of FreeNX.
Warnings occured during config check.
To enable these features please correct the configuration file.
<---- done
----> Testing your nxserver connection ...
Permission denied (publickey,gssapi-with-mic).
Fatal error: Could not connect to NX Server.
Please check your ssh setup:
The following are _examples_ of what you might need to check.
- Make sure "nx" is one of the AllowUsers in sshd_config.
(or that the line is outcommented/not there)
- Make sure "nx" is one of the AllowGroups in sshd_config.
(or that the line is outcommented/not there)
- Make sure your sshd allows public key authentication.
- Make sure your sshd is really running on port 22.
- Make sure your sshd_config AuthorizedKeysFile in sshd_config is set to
authorized_keys2.
(this should be a filename not a pathname+filename)
- Make sure you allow ssh on localhost, this could come from some
restriction of:
-the tcp wrapper. Then add in /etc/hosts.allow: ALL:localhost
-the iptables. add to it:
$ iptables -A INPUT -i lo -j ACCEPT
$ iptables -A OUTPUT -o lo -j ACCEPT
[root at tigertall ~]#
Thanks you!
2010-08-15
gaohu
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.centos.org/pipermail/centos/attachments/20100815/40ecafea/attachment-0002.html>
IIRC, nx defaults to /home/user/.ssh/authorized_keys2 whereas we always use /home/user/.ssh/authorized_keys. I would ensure nx is configured to look in the correct directory for the public key. We have zero windows boxes in my shop so I do not know how or if windows can be configured with key authorization. You could try temporarily enabeling password authorization on the server and see if that works. HTH, B.J. CentOS 5.5, Linux 2.6.18-194.11.1.el5 athlon 11:29:14 up 15:54, 1 user, load average: 0.07, 0.16, 0.15 On Sun, 2010-08-15 at 23:17 +0800, gaohu wrote:> I have installed freenx with this article > > http://wiki.centos.org/HowTos/FreeNX > > but when I use freenx-client on windows to connect to server, > I always get an "freenx Authentication failed." > > client err log output as this: > NX> 203 NXSSH running with pid: 1584 > NX> 285 Enabling check on switch command > NX> 285 Enabling skip of SSH config files > NX> 285 Setting the preferred NX options > NX> 200 Connected to address: 192.168.253.5 on port: 22 > NX> 202 Authenticating user: nx > NX> 208 Using auth method: publickey > NX> 204 Authentication failed. > > My sshd configed as use rsa key, and ssh soft like xshell can work > well. > > nxsetup output as this: Pleas care the following red commented two > line. I just think this is the point. > But why , and what shoud I do to solver ? > > [root at tigertall ~]# nxsetup --test > > ----> Testing your nxserver configuration ... > Warning: Could not find nxdesktop in /usr/bin. RDP sessions won't work. > Warning: Could not find nxviewer in /usr/bin. VNC sessions won't work. > Warning: Invalid value "APPLICATION_LIBRARY_PRELOAD=/usr/lib/libX11.so.6.2:/usr/lib/libXext.so.6.4:/usr/lib/libXcomp.so.2:/usr/lib/libXcompext.so:/usr/lib/libXrender.so.1.2". /usr/lib/libX11.so.6.2 could not be found. Users will not be able to run a single application in non-rootless mode. > Warning: Invalid value "DEFAULT_X_SESSION=/etc/X11/xdm/Xsession" > Users might not be able to request a default X session. > Warning: Invalid value "COMMAND_START_CDE=cdwm" > Users will not be able to request a CDE session. > Warning: Invalid value "COMMAND_SMBMOUNT=smbmount". You'll not be able to use SAMBA. > Warning: Invalid value "COMMAND_SMBUMOUNT=smbumount". You'll not be able to use SAMBA. > Error: Could not find 1.5.0 or 2.[01].0 or 3.[01].0 version string in nxagent. NX 1.5.0 or 2.[01].0 or 3.[012].0 backend is needed for this version of FreeNX. > > Warnings occured during config check. > To enable these features please correct the configuration file. > > <---- done > > ----> Testing your nxserver connection ... > Permission denied (publickey,gssapi-with-mic). > Fatal error: Could not connect to NX Server. > > Please check your ssh setup: > > The following are _examples_ of what you might need to check. > > - Make sure "nx" is one of the AllowUsers in sshd_config. > (or that the line is outcommented/not there) > - Make sure "nx" is one of the AllowGroups in sshd_config. > (or that the line is outcommented/not there) > - Make sure your sshd allows public key authentication. > - Make sure your sshd is really running on port 22. > - Make sure your sshd_config AuthorizedKeysFile in sshd_config is set to authorized_keys2. > (this should be a filename not a pathname+filename) > - Make sure you allow ssh on localhost, this could come from some > restriction of: > -the tcp wrapper. Then add in /etc/hosts.allow: ALL:localhost > -the iptables. add to it: > $ iptables -A INPUT -i lo -j ACCEPT > $ iptables -A OUTPUT -o lo -j ACCEPT > [root at tigertall ~]# > > > Thanks you! > > 2010-08-15 > > > ______________________________________________________________________ > > gaohu > > _______________________________________________ > CentOS mailing list > CentOS at centos.org > http://lists.centos.org/mailman/listinfo/centos-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos/attachments/20100815/be69822f/attachment-0002.html>
On Sun, Aug 15, 2010 at 11:17 AM, gaohu <tigerheight at gmail.com> wrote:> I have installed freenx with this article > > http://wiki.centos.org/HowTos/FreeNX > > but when I use freenx-client on windows to connect to server, > I always get an "freenx?Authentication?failed."You appear to have missed a step or configured the auth bits incorrectly. The NX user is the user who authenticates via ssh, and you authenticate via nx to the proper session. Go through the steps in the wiki again carefully and double check the logs to see who you're attempting to authenticate as. I'd bet you're trying to auth as your user instead of as the nx user and since the wiki states that only the nx user is authorized (via the AllowUsers nx statement) auth is failing for that reason. -- During times of universal deceit, telling the truth becomes a revolutionary act. George Orwell
On Sun, Aug 15, 2010 at 11:17 AM, gaohu <tigerheight at gmail.com> wrote:> I have installed freenx with this article > > http://wiki.centos.org/HowTos/FreeNX > > but when I use freenx-client on windows to connect to server, > I always get an "freenx Authentication failed."You appear to have missed a step or configured the auth bits incorrectly. The NX user is the user who authenticates via ssh, and you authenticate via nx to the proper session. Go through the steps in the wiki again carefully and double check the logs to see who you're attempting to authenticate as. I'd bet you're trying to auth as your user instead of as the nx user and since the wiki states that only the nx user is authorized (via the AllowUsers nx statement) auth is failing for that reason. -- During times of universal deceit, telling the truth becomes a revolutionary act. George Orwell _______________________________________________ CentOS mailing list CentOS at centos.org http://lists.centos.org/mailman/listinfo/centos =========================================================================My config as follows: 1. config sshd config, I add PasswordAuthentication no AllowUsers nx ---> nx is not an actual user in my system. 2. add user, I config nxserver --add user gaohu <--- gaohu is a common user on my system, and can connect via ssh with isa key , (and password also works before I use ssh key to audit.) then re config sshd config file, set AllowUsers nx gaohu one thing I can not understand is sshd default use /home/myuser/.ssh/authorized_keys, file but nxserver generate the key at /home/myuser/.ssh/authorized_keys2 file, should I do other settingsin sshd config file to support this? 3.then I install the client and copy /etc/nxserver/client.id_dsa.key file contentto the key window. That's all. but when I run nxserver --test ? I just got permission denied ? why? following is my sshd_config file, Could any one help? ========================================================= # $OpenBSD: sshd_config,v 1.73 2005/12/06 22:38:28 reyk Exp $# This is the sshd server system-wide configuration file. See# sshd_config(5) for more information.# This sshd was compiled with PATH=/usr/local/bin:/bin:/usr/bin# The strategy used for options in the default sshd_config shipped with# OpenSSH is to specify options with their default value where# possible, but leave them commented. Uncommented options change a# default value.#Port 22#Protocol 2,1Protocol 2#AddressFamily any#ListenAddress 0.0.0.0#ListenAddress ::# HostKey for protocol version 1#HostKey /etc/ssh/ssh_host_key# HostKeys for protocol version 2#HostKey /etc/ssh/ssh_host_rsa_key#HostKey /etc/ssh/ssh_host_dsa_key# Lifetime and size of ephemeral version 1 server key#KeyRegenerationInterval 1h#ServerKeyBits 768# Logging# obsoletes QuietMode and FascistLogging#SyslogFacility AUTHSyslogFacility AUTHPRIV#LogLevel INFO# Authentication:#LoginGraceTime 2m#PermitRootLogin yes#StrictModes yes#MaxAuthTries 6RSAAuthentication yesPubkeyAuthentication yesAuthorizedKeysFile .ssh/authorized_keys # For this to work you will also need host keys in /etc/ssh/ssh_known_hosts#RhostsRSAAuthentication no# similar for protocol version 2#HostbasedAuthentication no# Change to yes if you don't trust ~/.ssh/known_hosts for# RhostsRSAAuthentication and HostbasedAuthentication#IgnoreUserKnownHosts no# Don't read the user's ~/.rhosts and ~/.shosts files#IgnoreRhosts yes# To disable tunneled clear text passwords, change to no here!#PasswordAuthentication yes#PermitEmptyPasswords noPasswordAuthentication no AllowUsers nx gaohu# Change to no to disable s/key passwords#ChallengeResponseAuthentication yesChallengeResponseAuthentication no# Kerberos options#KerberosAuthentication no#KerberosOrLocalPasswd yes#KerberosTicketCleanup yes#KerberosGetAFSToken no# GSSAPI options#GSSAPIAuthentication noGSSAPIAuthentication yes#GSSAPICleanupCredentials yesGSSAPICleanupCredentials yes# Set this to 'yes' to enable PAM authentication, account processing, # and session processing. If this is enabled, PAM authentication will # be allowed through the ChallengeResponseAuthentication mechanism. # Depending on your PAM configuration, this may bypass the setting of # PasswordAuthentication, PermitEmptyPasswords, and # "PermitRootLogin without-password". If you just want the PAM account and # session checks to run without PAM authentication, then enable this but set # ChallengeResponseAuthentication=no#UsePAM noUsePAM yes# Accept locale-related environment variablesAcceptEnv LANG LC_CTYPE LC_NUMERIC LC_TIME LC_COLLATE LC_MONETARY LC_MESSAGES AcceptEnv LC_PAPER LC_NAME LC_ADDRESS LC_TELEPHONE LC_MEASUREMENT AcceptEnv LC_IDENTIFICATION LC_ALL#AllowTcpForwarding yes#GatewayPorts no#X11Forwarding noX11Forwarding yes#X11DisplayOffset 10#X11UseLocalhost yes#PrintMotd yes#PrintLastLog yes#TCPKeepAlive yes#UseLogin no#UsePrivilegeSeparation yes#PermitUserEnvironment no#Compression delayed#ClientAliveInterval 0#ClientAliveCountMax 3#ShowPatchLevel no#UseDNS yes#PidFile /var/run/sshd.pid#MaxStartups 10#PermitTunnel no#ChrootDirectory none# no default banner path#Banner /some/path# override default of no subsystemsSubsystem sftp /usr/libexec/openssh/sftp-server ========================================================== -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos/attachments/20100816/ec5443e8/attachment-0002.html>
gaohu wrote:> I have installed freenx with this article > > http://wiki.centos.org/HowTos/FreeNX > > but when I use freenx-client on windows to connect to server, > I always get an "freenx Authentication failed." > > client err log output as this: > NX> 203 NXSSH running with pid: 1584 > NX> 285 Enabling check on switch command > NX> 285 Enabling skip of SSH config files > NX> 285 Setting the preferred NX options > NX> 200 Connected to address: 192.168.253.5 on port: 22 > NX> 202 Authenticating user: nx > NX> 208 Using auth method: publickey > NX> 204 Authentication failed. > > My sshd configed as use rsa key, and ssh soft like xshell can work well. > > nxsetup output as this: Pleas care the following red commented two line. > I just think this is the point. > But why , and what shoud I do to solver ?It doesn't use your key - it connects as the nx user first. All you should have to do is push the 'key' button when configuring the client for that host and paste in the contents of /etc/nxserver/client.id_dsa.key from the server. Unlike the commercial server, freenx generates a unique key for each host. -- Les Mikesell lesmikesell at gmail.com