This is an old revision of the document!
This page contains some suggestions on how to improve your SSH experience.
You user own configuration file is located in your home folder at the path
In some cases this file does not exist, you can create it for example by issuing
This file is very useful to create ssh shortcuts to servers and add specific options for each server. In what follows I show some examples of how this can be used.
One can speedup logging in by configuring her/his own ssh client. This will also help in scp-ing data to the cluster.
The configuration example below shows how you can access a machine through another machine with a single ssh command. The scenario is as follows:
User ---> machine hostA.matfys.lth.se ----> machine hostB.matfys.lth.se ----> machine hostC.matfys.lth.se
And you want to use one single command to login to B or C.
# access hostA.matfys.lth.se Host hostA HostName hostA.matfys.lth.se User <username on hostA.matfys.lth.se> ForwardX11 yes # this is equivalent to ssh -X hostA.matfys.lth.se # directly access hostB.matfys.lth.se Host hostB User <Username on hostA.matfys.lth.se> ForwardX11 yes # Use this command if A uses Openssh server version < 5.4. # It requires the program netcat (nc) to be installed on the # hostA.matfys.lth.se machine. ProxyCommand ssh -q hostA.matfys.lth.se nc hostB.matfys.lth.se 22 # directly access hostC.matfys.lth.se Host hostC User <Username on hostC.matfys.lth.se> ForwardX11 yes # Use this command if hostB.matfys.lth.se uses Openssh server version >= 5.4, # that has native support for tunnelling ssh connections. ProxyCommand ssh -q hostB.matfys.lth.se -W hostC.matfys.lth.se:22
Example: My user is florido. In the template above, I would change all the <Username …> to florido.
then to login to
hostB.matfys.lth.se I will do:
And I will have to input 2 passwords: one for
hostA.matfys.lth.se, one for
In general you will have to input as many passwords as the number of hops. To overcome this problem, use a private/public ssh keypair technique described below.
If you plan to use this, read the following:
|DO NOT USE PASSWORDLESS KEYS. THESE ARE A SECURITY THREAT FOR THE EVERYONE USING SERVERS!!!|
This tutorial is nice:
the below part of the document is work in progress.
SSH key pair is a form of PKI, Public Key Infrastructure. In this technology every user or machine has a pair of keys:
These user keys are usually stored in the user's
~/.ssh/ folder, the default names are
id_rsa (private) and
id_rsa.pub (public). But one can choose any location and any name.
The machine keys are usually stored in the
/etc/ssh/ system folder, and they are generated at installation time by the OpenSSH scripts. They are of different kinds as they support different encryption schemas,
their names being like ssh_host_<schema> (private) and ssh_host_<schema>.pub (public).
In the example below, note how the private key is readable and writable ONLY by root while all the
.pub ones are readable by everyone (but not writable!)
ls -ltrah /etc/ssh/ssh_host* -rw-r--r-- 1 root root 393 mar 30 2016 /etc/ssh/ssh_host_rsa_key.pub -rw------- 1 root root 1,7K mar 30 2016 /etc/ssh/ssh_host_rsa_key -rw-r--r-- 1 root root 601 mar 30 2016 /etc/ssh/ssh_host_dsa_key.pub -rw------- 1 root root 672 mar 30 2016 /etc/ssh/ssh_host_dsa_key -rw-r--r-- 1 root root 173 mar 30 2016 /etc/ssh/ssh_host_ecdsa_key.pub -rw------- 1 root root 227 mar 30 2016 /etc/ssh/ssh_host_ecdsa_key -rw-r--r-- 1 root root 93 mar 30 2016 /etc/ssh/ssh_host_ed25519_key.pub -rw------- 1 root root 399 mar 30 2016 /etc/ssh/ssh_host_ed25519_key -rw-r--r-- 1 root root 651 maj 10 2016 /etc/ssh/ssh_host_key.pub -rw------- 1 root root 986 maj 10 2016 /etc/ssh/ssh_host_key
Every ssh pki key has a fingerprint, that is, a unique way to identify that key. You can check your machine unique fingerprint by using the
ssh-keygen script provided by OpenSSH:
The overall mechanism is as follows. A user willing to connect to a server has to
OpenSSH on linux provides a set of scripts for managing keys:
the above part of the document is work in progress.