[prev in list] [next in list] [prev in thread] [next in thread] 

List:       freenx-knx
Subject:    Re: [FreeNX-kNX] FreeNX with SSH key authentication fails
From:       Jeremy Wilkins <wjeremy () shaw ! ca>
Date:       2009-11-09 23:22:42
Message-ID: 26275582.post () talk ! nabble ! com
[Download RAW message or body]


This doesn't solve the public key authentication issues that he mentioned.

It just changes the NX user public key which ALL users need in their NX
client after the changes you suggest.  Paul wants the users to authenticate
via public key which is entirely different.

Paul:  The only way I know that this will work is by using the open source
client, with freenx in su authentication mode, but I may be wrong.  As far
as I know the NoMachine client won't work for that yet.  That may change in
the near future hopefully.  Meanwhile what Les mentioned is nearly as
secure.


Les Mikesell-2 wrote:
> 
> Paul van Gerven wrote:
> > I fiddled with FreeNX for a whole weekend, but I cannot get it set up 
> > the way I want. I can either setup SSH to exclusively accept keys as an 
> > authentication method, but then FreeNX will not login, or I tell SSH to 
> > accept password authentication, in which case FreeNX does work. The 
> > latter situation is fine on a LAN behind a router, but obviously not 
> > safe when the server is exposed to internet.
> > 
> > Here's what I did to get to the latter situation:
> > 1) Install a OpenSSH server on Ubuntu Jaunty and left the configuration 
> > at default.
> > 2) Install the FreeNX from the repo on launchpad and ran 
> > /usr/lib/nx/nxsetup --install. I opted for the default keys.
> > 3) During step 2, FreeNX asks me to add
> > 
> > AuthorizedKeysFile /var/lib/nxserver/home/.ssh/authorized_keys2 and 
> > PasswordAuthentication yes
> > 
> > to sshd_config, and I did.
> > 
> > Can someone walk me through the steps I need to take next to disable 
> > password authentication again, and tell SSH to authenticate only with 
> > keys I generate myself, while keeping FreeNX functional?
> > 
> > If I properly set up SSH first, i.e. to exclusively use keys I generated 
> > myself, and then install FreeNX, the client from NoMachine gives an 
> > authentication failed message.
> > 
> > Other than this minor problem (for a newbie like me) FreeNX is 
> > impressive. It is so much faster than VNC!
> 
> Just replace the embedded key in the NX client with the public key that 
> freenx generates (configure, then press the 'key' button and paste in 
> the replacement). In Ubuntu-land this should be found somewhere under 
> /var/lib/nxserver/home/.
> 
> -- 
> Les Mikesell
> lesmikesell@gmail.com
> ________________________________________________________________
> 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@kde.org
> https://mail.kde.org/mailman/listinfo/freenx-knx
> ________________________________________________________________
> 
> 

-- 
View this message in context: \
http://old.nabble.com/FreeNX-with-SSH-key-authentication-fails-tp26274389p26275582.html
 Sent from the freenx-knx mailing list archive at Nabble.com.

________________________________________________________________
     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@kde.org
      https://mail.kde.org/mailman/listinfo/freenx-knx
________________________________________________________________


[prev in list] [next in list] [prev in thread] [next in thread]