How to Connect to Remote Servers Without Typing a Password

For operations engineers who routinely connect to remote servers via SSH, the hassle of entering passwords on cold terminals during late hours can be quite annoying. The solution lies in SSH key authentication, which eliminates the need for passwords and offers numerous advantages. This guide outlines how to implement SSH key authentication in under five minutes, without relying on graphical tools or expensive software, using only the command line.

The primary benefit of SSH key authentication over passwords is that it provides superior brute-force resistance, making it virtually impossible for attackers to crack a 4096-bit RSA key, which contains more possible combinations than all the atoms in the observable universe. Additionally, SSH key authentication is convenient, allowing for seamless access to remote servers with a single command, and is ideal for audit purposes as each key is easily traceable to a specific user or machine.

Moreover, it is perfectly suited for automation tasks such as scripts, CI/CD pipelines, and Ansible playbooks.

The process begins with generating an SSH key pair using the command `ssh-keygen -t ed25519 -C "your_email@example.com"`. The `-t ed25519` option specifies the use of the Ed25519 algorithm, which is both faster and more secure than the older RSA algorithm. When prompted, choose the default file location (`~/.ssh/id_ed25519`) and create a strong passphrase to encrypt the private key on disk.

Two files are created: `~/.ssh/id_ed25519`, your private key (keep it secret), and `~/.ssh/id_ed25519.pub`, your public key (share it freely).

Next, copy the public key to the remote server using either the `ssh-copy-id` command or by manually adding it to the `~/.ssh/authorized_keys` file. After copying the public key, test the connection using the `ssh username@server_ip` command. If successful, verify the configuration by checking file permissions, ensuring the correct private key is being used, and hardening the server by disabling password authentication and enabling public key authentication. Remember to rotate keys every 90 days for optimal security.

With SSH key authentication, you can streamline and secure your remote server access, significantly reducing password-related frustrations and enhancing overall system security.