FreeNX
Obtain freenx from www.nomachine.org. On the server side, one will need nxserver, nxnode, and nxclient. On the client side, only nxclient is needed. Freenx has some weird design when all communication happens over a ssh session started with a "nx" account. The keys for this user is under ~nx/.ssh.Suppose one implemented key-only authentication, how does one login when the nomachine client gui only allows password authentication? It seems that nxserver can maintain its own password database. On my ubuntu installation, this can be enabled by setting the following in /usr/NX/etc/server.cfg:
EnablePasswordDB = "1"
Then use the nxserver to create a user when the program will prompt you for a password:
$ /usr/NX/bin/nxserver --useradd some_user NX> 900 Setting password for user: some_user. NX> 102 Password: NX> 102 Confirm password:
Once that's setup, the nx account can authenticate using key, and the user login can be done against the nx password db. Not the smartest thing but it is what it is.
The information below is quite outdated.
FreeNX server and client
FreeNX is a secure remote control software. It supports Linux, Solaris, and FreeBSD on the server side, and almost all platform on the client side. For this knowledge, I'm using Fedore C6 as my server, and Windows XP as my client.Installing the NX server
Couldn't be easier, just do a yum install would be all.yum install freenx
Installing the NX client
Client can be downloaded from http://freenx.berlios.de/clients.php. Just download and install it.Configuring authentication
The biggest challenge is probably authentication. On the server, as root docd ~nx/.ssh ssh-keygen -t rsa -b 2048 #save the key as ./id_rsa echo id_rsa.pub >> authorized_keys chown nx id_rsa*
Next, copy id_rsa to your nxclient's connection profile, and you're set.
There are no comments on this page. [Add comment]