From ArchWiki
Revision as of 03:20, 24 July 2005 by Cactus (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

From the berliOS website:

FreeNX is a free server implementation of OSS NX components. NX allows usage of X-connections over real slow links like a Modem or ISDN.

To install FreeNX server on your Arch Box, please download one of the Following:

  • A PKGBUILD file from the AUR and make the package yourself
  • A pre-build package from cactus' repo

(I am assuming the latest version i.e. 0.4.x)

Follow the instructions at the Post-install to complete the post install configuration. Namely, you will need to add the users to the FreeNX server that you want to allow access from outside.

You will also need to download a client for the FreeNX server. The client can be downloaded from's website. Clients are available for both, Linux and Windows.

Once you have installed the FreeNX server on your machine, you need to modify some of the RSA keys.

1. cd /usr/NX/bin 2. Modify nxloadconfig:

  • Change NX_AUTHORIZED_KEY=.ssh/authorized_keys2 to NX_AUTHORIZED_KEY=.ssh/authorized_keys

3. rm /usr/NX/home/nx/.ssh/authorized_keys2 4. Make a new Keypair:

 ssh-keygen -d
  --> into: /usr/NX/home/nx/id_dsa
  --> no passphrase

5. Copy the public key to the authorised key file

 cat /usr/NX/home/nx/ > /usr/NX/home/nx/.ssh/authorized_keys

6. Securely transfer the id_dsa file to the client as its private key 7. Say you added user1 to the FreeNX server, and user1 is a linux user too, then you need to do the following for the FreeNX server to complete authentication:

cat /home/user1/.ssh/authorizedkeys2 > /home/user1/.ssh/authorizedkeys
rm /home/user1/.ssh/authorized_keys2

You should be done. Try to connect to the server from the client now.

P.S. cactus suggests that you set the connection speed on the client to Modem, even if you have a better connection, so that all kinds of compression is turned on and you get a really fast connection.