SSH

Configure
The settings of these section need to be writen in file

Custom port
SSH server are a common target for hackers. Changing the port away from the default will greatly reduce the noise in your logs.

Authentication
Let's limit the users that have access to the server using ssh.

Crypo
These settings are derived from secure secure shell.

KeepAlive
To make sure connections do not freeze in case of inactivity.

Generate server keys
Modify file  and make sure that the only lines to contains HostKey are:

Publish server keys
It is possible to publish the fingerprint of your ssh server keys in a DNS server. It allows to not have to blindly trust the key on first connection.

To get the records to publish in your dns server, run

Once published, you can check you records with

Now you can configure your client to use your published keys.

Restart
Restarting the SSH server while connected through SSH is usually safe. However, you need to take some precautions to avoid being locked out of your server. Make sue you do that from a stable internet connection: in case your SSH server doesn't restart correctly, you don't want your active SSH connection to drop while you fix the issue. If you are connected through SSH, test that your server restarting correctly by opening a second connection The  option prevents the SSH client from reusing your active connection in case you have multiplexing enabled.

Fail2ban
Fail2ban configuration for ssh is active by default in Debian. However, if you changed the listening port of your server, you must reflect that in fail2ban. To do so, create file  with the following content

Configure
The settings of these section need to be written in file. Unless they contains a, they must be set under the existing   section.

Shortcuts
When it comes to typing, my motto is less is more. The following setting allows you to type  instead of

Port
If you changed the port of your servers, this settings allows you client to use the correct port automatically.

Crypo
These settings are derived from secure secure shell.

Generate user keys
This needs to be run by all users. It is strongly recommended to set a password to your keys. A passwordless keyfile is as secure as a post-it on the wall with your password. If a script need unattended access to another machine, create dedicated accounts and key for that usage.

Verify published server key
Make sure your server has some published keys.

Edit file  and add the line