[FreeNX-kNX] Fwd: Re: NXClient fails to connect with authentication failed for user.

[Dion Moult]

Tried changing that, restarting sshd and nxserver, but it still gives the same 
error:

sshd[23560]: Connection from 127.0.0.1 port 38026
sshd[23560]: Failed none for nx from 127.0.0.1 port 38026 ssh2
sshd[23560]: Found matching DSA key: blahblahblahetcetc
sshd[23560]: Accepted publickey for nx from 127.0.0.1 port 38026 ssh2
sshd[23560]: pam_unix(sshd:session): session opened for user nx by (uid=0)
sshd[23560]: User child is on pid 23562
nxserver[23692]: (nx) Failed login for user=dion from IP=127.0.0.1
sshd[23562]: Connection closed by 127.0.0.1
sshd[23562]: Transferred: sent 2848, received 1968 bytes
sshd[23562]: Closing connection to 127.0.0.1 port 38026
sshd[23560]: pam_unix(sshd:session): session closed for user nx

On Saturday 26 September 2009 09:55:03 you wrote:
> ----------  Forwarded Message  ----------
> 
> Subject: Re: [FreeNX-kNX] NXClient fails to connect with authentication
>  failed for user.
> Date: Friday 25 September 2009
> From: "ChrisB" <chris at ccburton.com>
> To: User Support for FreeNX Server and kNX Client <freenx-knx at kde.org>
> 
> Dion Moult <dion at thinkmoult.com> wrote on 25/09/2009 18:09:17:
> 
> 
> SNIP
> 
> > sshd[13479]: Connection from 127.0.0.1 port 40791
> > sshd[13479]: Found matching DSA key: blahblahblahblah
> > sshd[13479]: Accepted publickey for nx from 127.0.0.1 port 40791 ssh2
> > sshd[13479]: pam_unix(sshd:session): session opened for user nx by
> 
> (uid=0)
> 
> > sshd[13479]: User child is on pid 13481
> > nxserver[13611]: (nx) Failed login for user=dion from IP=127.0.0.1
> 
> Yup
> 
> > I have checked that the public key is in /home/dion/.
> > ssh/authorized_keys. If I
> > do ssh -p 443 localhost on the computer with the account dion it asks
> 
> for my
> 
> > passphrase of my private keypair (not the NX one) and I can log in and
> 
> SSH in
> 
> You need to use password authentication for the local user after
> connecting via ssh as user nx.
> 
> Some distros disable this by default because it allows brute force attacks
> . . . .
> 
> > remotely fine without problems. I'm not sure whether it helps but when I
> 
> try
> 
> > ssh -p 443 nx at localhost it asks for a Password, of which nothing I
> > try can log
> > it in.
> >
> > This is my sshd_config:
> > Port 443
> > Protocol 2
> > SyslogFacility AUTH
> > PermitRootLogin no
> > RSAAuthentication yes
> > PubkeyAuthentication yes
> > PasswordAuthentication no
> 
> Here
> 
> Just change to PasswordAuthentication  yes
> 
> > PermitEmptyPasswords no
> > UsePAM yes
> > Compression yes
> > KeepAlive yes
> > ClientAliveInterval 30
> > ClientAliveCountMax 4
> > AuthorizedKeysFile      .ssh/authorized_keys
> > LogLevel VERBOSE
> >
> > (Note: I run SSH on port 443 on purpose, not by accident)
> >
> > Summary: When trying to connect using username and password for the
> 
> account
> 
> > "dion" which exists on the box running freenx it says Authentication
> 
> failed
> 
> > for user dion.
> >
> > Any ideas? Much appreciated.
> 
> ________________________________________________________________
> 
> >      Were you helped on this list with your FreeNX problem?
> >     Then please write up the solution in the FreeNX Wiki/FAQ:
> 
> http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ
> 
> >          Don't forget to check the NX Knowledge Base:
> >                  http://www.nomachine.com/kb/
> >
> > ________________________________________________________________
> >        FreeNX-kNX mailing list --- FreeNX-kNX at kde.org
> >       https://mail.kde.org/mailman/listinfo/freenx-knx
> > ________________________________________________________________
> 
> -------------------------------------------------------
> 
-- 
Dion Moult :-)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/freenx-knx/attachments/20090926/32017a53/attachment.sig>