Quick Tip

Master `ssh` for Secure and Efficient Remote Access

Challenge: Repeatedly typing long hostnames and usernames for SSH connections is tedious and error-prone. Managing multiple SSH keys for different servers adds another layer of complexity.

The Solution: Leverage the power of the `~/.ssh/config` file to define aliases and configurations for your SSH connections.

Host myserver HostName 192.168.1.100 User admin Port 2222 IdentityFile ~/.ssh/my_private_key Host anotherhost HostName server.example.com User deployer ForwardAgent yes

Why it works: This configuration file allows you to create custom shortcuts (like `myserver` or `anotherhost`) that expand into detailed connection parameters. `ssh` automatically reads this file, so you can simply type `ssh myserver` to connect.

Pro-Tip: Use `ForwardAgent yes` to securely forward your SSH agent credentials, allowing you to use keys stored on your local machine for authentication on remote servers without copying the private key itself.

Linux Tips & Tricks | © ngelinux.com | 4/28/2026