SSH troubleshooting

From EnGardeWiki

When trying to connect to EnGarde Secure Linux via SSH you may see errors similar to:

The authenticity of host 'meatwad (192.168.1.23)' can't be established.
RSA1 key fingerprint is FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF.
Are you sure you want to continue connecting (yes/no)?

EnGarde ships, by default, with SSH password authentication disabled. This means that you have to have a valid RSA keypair setup (the public key on the server, the private key on your local machine) and you must use this RSA keypair to SSH in. You can set up keys for the root user via the Guardian Digital WebTool by using the Secure Shell Management module located under the Services Menu. If you need to set up keys for a user other than root, you must use the Guardian Digital User Manager.

You will be asked to download a PRIVATE key which you then tell your local SSH client to use while connecting. Most, if not all, Linux distributions ship with an SSH client, if you need an SSH client for Windows we suggest using PuTTY. Be sure to download the PuTTYgen utility as well, as the keys provided by EnGarde Secure Linux must be modified by this utility in order to work properly with PuTTY.

An alternative approach is to enable password authentication. We do not suggest this for security reasons, which is why we ship EnGarde Secure Linux with the feature disabled. If you must enable it, and you understand the risks, it can be enabled in the Secure Shell Management module of the WebTool.

Another piece of the puzzle is that your client's IP address must be allowed to connect via SSH in the Access Control module of the WebTool.