

# NX-private-key: Key-based authentication.

# Supported methods for connections by NX protocol are: To specify a subset of methods use a comma-separated # default all the available methods are supported. # Specify how clients will have to authenticate to the server, by On the server, edit server.cfg ( sudo gedit /usr/NX/etc/server.cfg) and find this section: # Note: On Linux, server.cfg is located here: "/usr/NX/etc/server.cfg".


Generate a new private/public key pair from the client run this from the client: ssh-keygen -t rsa -b 4096 -C "your personal comment or email"Ĭopy the public (.pub) key only from client to server run this from the client notice the renaming of the file on the destination to avoid conflict with keys already generated on the server: scp ~/.ssh/id_rsa.pub Run from server:Īdd public key now on server to proper NoMachine file run this from the server: cat ~/.ssh/id_rsa_nxclient.pub > ~/.nx/config/authorized.crtĪnd lastly set this file's permissions to 0600 to enable read/write on this file ONLY for the user (owner) of this file, for security: chmod 0600 ~/.nx/config/authorized.crt Here's one example of commands to do that: How to set up key based authentication with NX protocolĮssentially, just add your public key to the $HOME/.nx/config/authorized.crt file on the server.To enable key-based authentication to server: It is not open source, but is no cost to use (personal use only-businesses must pay). NoMachine is an excellent remote login program, with excellent file-sharing/mount abilities and excellent cross-platform support for Windows, Mac, Linux, iOS, Android, Raspberry Pi, and ARM. If you ever need to ssh in, I've documented my various ssh notes here. I originally posted these instructions on my eRCaGuy_dotfiles repo here:
