As well as having to type passphrases, remembering the right user, key file, port and other settings for each host you want to SSH into might quickly become overwhelming.
That’s why, in addition to the command line options we saw so far, SSH also allows to read the same options from configuration files.
The configuration data will be applied from the following sources in the following order:
- command-line options
- user’s configuration file (located in
- system-wide configuration file (located in
How to write
The configuration files are split into sections, each representing a Host specification. Each section allows us to define a server we’ll frequently want to connect to and give it a pet name, so that we can specify some default parameters for it.
Let’s take for example this command to SSH into
$ ssh -i ~/ssh/my_key_with_a_long_name_id_rsa -p 1337 email@example.com
Instead of typing all of that out each time we want to connect, we can put a Host specification in
Host myserver HostName server.123.mydomain.com User myusername Port 1337 IdentityFile ~/ssh/my_key_with_a_long_name_id_rsa
And then connect in the future simply with
$ ssh myserver
You can also use wildcards in the value for
, meaning you can use
Host * Key Value ...
to specify parameters for all hosts, or even for example
Host i-* Key Value ...
to specify parameters for all hosts which have the name of Amazon EC2 instances.
This is just a basic example, but an important thing to note is that you can specify just about any parameter in SSH configuration files. In fact, there are even a few advanced configuration parameters which are unavailable as command line arguments.
In order to still allow to use them on the command line, SSH offers the special flag:
$ ssh -oParameterKey="ParameterValue" myuser@myserver
So it is definitely worth taking a look at the complete list in case they are ever needed.
See the man page for more info.