[FreeNX-kNX] Authentication failed with NX client ... MORE TESTS ..

[Michael Hoeller]

Hello,

I have done a lot of tests and changes, but I was not able to get a 
connect. I have summarized the main isses - maybe this rings a bell to 
someone - I am lost an close to give up...

On the remote machine NXSERVER (SuSE 9.2) I have uninstalled the 
NXSEERVER und reinstalled.




I got the following info at the end:

Searching for nxserver binary...done
Setting up /etc/nxserver/ ...done
Setting up /var/lib/nxserver/ ...done
Setting up known_hosts and .ssh/authorized_keys2 ...Unique key 
generated; your users must install

    /home/.nx//.ssh/client.id_dsa.key

on their computers.
done
Setting up permissions ...done
Ok, nxserver is ready.

PAM authentication enabled:
  All users will be able to login with their
  normal passwords.

You can change this behaviour in the nxserver script.

Warning: Clients will not be able to login to this server with the 
standard key.
         Please replace /usr/NX/share/client.id_dsa.key on all clients 
you want
         to use with the private key 
from /home/.nx//.ssh/client.id_dsa.key and
         protect it accordingly.

If you really want to use the NoMachine key please 
remove /home/.nx//.ssh/authorized_keys2 and run this script with the 
parameter --setup-nomachine-key again.
Have Fun!

I have replaced  /usr/NX/share/client.id_dsa.key (Client) with 
/home/.nx//.ssh/client.id_dsa.key from the remote NX SERVER.


I checked if the SERVE is running

# nxserver --status
NX> 100 NXSERVER - Version 1.4.0-02 OS_(GPL)
NX> 110 NX Server is running
NX> 999 Bye


I imported the /usr/NX/share/client.id_dsa.key to the nomachine client.

I tried to connect an get the following messae:

NX> 203 NXSSH running with pid: 8395
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.55.100 on port: 22
NX> 202 Authenticating user: nx
NX> 208 Using auth method: publickey
NX> 204 Authentication failed.

but I can log in with ssh -X user at 192.168.55.100

with tail -f /var/log/* and the LogLevel set to DEBUG3 I do not see a 
message. 

THere must be something basically false
a) do I have the correct key in the client?

b) I think sshd is the problme but I can not find what's false
   the message is faily clear that the authentication is not ok
   can I do the same command, wich is used in NX, at the commanline to
   get the connection. This might give a hint.


Hope some one can help.
Michael


On Mittwoch, 29. August 2007, Fabian Franz wrote:
> > Hello,
> >
> > now I am lost... seems that I need some help...
> > michael at akazia:~/.ssh> ssh -i /usr/NX/share/keys/server.id_dsa.key
> > nx at 192.168.55.100
>
> I think there might a problem in your sshd setup. To find the reasonb
> edit sshd_config, set the loglevel higher and look into
> /var/log/auth.log or /var/log/daemon.log.
>
> If you are unsure just do:
>
> tail -f /var/log/*
>
> And then connect new.
>
> It might say something like key has not right permissions or anything
> like that. If that is the case, fix it ;-).
>
> But anyway, SSHD logging is your friend here.
>