SSH is not supported natively on Windows so an SSH client must be installed. PuTTY is an excellent and actively developed open source SSH client. PuTTY’s home page is located here:
The latest 32bit version (which will work on 64bit and 32bit processors) is always available from this this link.
The file that is linked to is a standalone binary so does not require installing and will simply run when double clicked.
When PuTTY is opened it will display the basic options page. A linux server can be logged into from this page by entering the hostname or IP address of a server in the “Host Name” field. Shown here:
Then click the “Open” button at the bottom. The first time that you connect to a new server (or after a server is re-imaged or re-installed) the following warning will appear:
Hit “Yes” to continue connecting. A command line terminal will open with a prompt to enter a username:
Enter the user that you want to log in as and hit Enter. You will then be prompted for the password and logged into the server’s command line.
The simple connection described above requires manually entering the hostname or IP address and authentication details for every connection. PuTTY provides a mechanism to save a connection and all its setting for quick access. PuTTY calls these saved connections “Sessions”.
The process for creating a saved sessions is as follows:
A saved session will be displayed under “Default Settings” when PuTTY is opened:
In order to use a saved sessions:
Or, simply double-click on the saved session name.
A session can be updated to include new configuration once it has been created. In order to do this:
The session will now include any new settings such as those described below.
Putty can be configured to automatically enter a username when logging into a server. This is done as follows:
A secure protocol, in addition to encryption, demands that authentication. The two principle ways of doing this with SSH are:
Password authentication is the default method for logging in via SSH and will be enabled by default on all Memset servers. Password authentication is secure but there are several advantages to disabling password authentication and instead relying on SSH keys. SSH keys are more secure than passwords as they are all but impossible to brute force attack on the server end. An attacker must have access to the private key to log into the server. They are also more efficient because any server that has the public key can be logged into from any computer that has the private key. This means that a single key (and password) can be used to securely log into any number of servers.
Every SSH key pair is unique. Therefore, in order to start using an SSH key pair they must first be generated.
PuTTY cannot generate a key pair, however, PuTTY’s author has also written a tool to generate a key pair suitable to use in PuTTY. This tool is called PuTTYGen. The latest version is always available via this link.
When PuTTYGen is opened it will default to the following parameters for an SSH key pair:
RSA refers to the encryption algorithm and 2048 bits is the length of the key. A longer key is more secure but incurs a performance penalty. However, with modern computers, a key length of 4096 bits will not cause any noticeable performance issues and will be secure for a much longer time as attackers computers get more powerful.
Therefore, a bit length of 4096 should be entered into the “Number of bits in the generated key” field.
Create the new key by hitting the “Generate” button. When the keys have been generated you will see the following screen:
In order to save the key pair:
Now is also a good time to save both files (or their contents) into a password manager for secure portability.
SSH keys can only be used once the public key has been copied to the server. It must be added to the ~/.ssh/authorized_keys file of the user you intend to log in as.
In order to do this log into your server via SSH using a username and password. Then open the authorized_keys file with your favourite text editor, nano is shown here:
cd .ssh nano authorized_keys
Then paste the entire public key shown above in the PuTTYGen save screen. The public key must only occupy a single line. Then exit the server.
Next, open PuTTY and load the session for that server. Then expand the SSH category and highlight the “Auth” section. Hit the “Browse” button and find the private key you saved from PuTTYGen.
Before hitting “Open” go back to the “Session” page and click “Save”. The key will always now be used for this session.
Finally, hit “Open”. You will be prompted for the password of the private key and not the password for the server.
This method of using the SSH keys means that the key’s password must be entered every time a connection is opened. However, it will always be the same password i.e. the key’s password, no matter which server is being logged into. This is convenient in that only a single password needs to be remembered.
However, this process can be further streamlined by loading the key into memory so that a password is only required a single time and not for every connection.
When an SSH key is loaded into memory it will be available for use whenever a new connection is made to a server. PuTTY will automatically check for the presence of a loaded key when it initiates a new connection and will use it automatically, without prompting for a password, if one is present.
PuTTY cannot load the key into memory but a program by the same developer does. This program is called Pageant. The latest binary is available from this link.
Pageant is a simple program that only loads private SSH keys. All that is required to do so is to hit the Add key button, locate the private key and open it.
Once the private key that was created with PuTTYGen is opened and loaded with Pageant it looks like the following:
Pageant can load multiple private keys.
PuTTY will attempt to use all the private keys loaded into memory with Pageant when making a connection to a server. If the private key is loaded with Pageant and the username already configured in PuTTY a connection will be made without requiring any user input.
Furthermore, WinSCP, an FTP replacement, will also use any keys loaded into Pageant. WinSCP is a recommended replacement for FTP under Windows. Please see the Replacing FTP with SSH documentation for instructions on using WinSCP.
The security benefits of using SSH keys can be maximised by disabling password authentication on the server. Almost all of the simple automated attacks against SSH are people or bots attempting to guess username and password combinations. When password authentication is disabled this method of attack is rendered useless. It is, therefore, highly recommended to disable password authentication on the server.
Before you follow the steps below, make sure you have a copy of your server's root password as it will be required to regain access to the server if there are any problems with SSH as a result of this work.
The steps to disable password authentication are as follows:
Before edit: PasswordAuthentication yes After edit: PasswordAuthentication no
systemctl restart sshd.service
If you are not able to log back into the server Memset provides an out-of-band access to all their servers via MemShell. Please refer to the MemShell documentation for more information. The root password for your server will be required to access the server via MemShell.
Last updated 22 June 2017, 06:53 GMT