The SSH config is a powerful tool to get \"more\" out of your normal SSH connection.<\/p>\n
Just create an file called \"config\" in your .ssh folder and it will be used on a new SSH session.<\/p>\n
Lets start with a simple example of how a connection configuration could look like:<\/p>\n
Host myHost\n Hostname 1.2.3.4 \n IdentityFile ~\/.ssh\/myHostKey\n User myUser<\/pre>\nWith this code, an \"ssh myHost\" will try to connect to the host 1.2.3.4 - using the user myUser and the keyfile myHostKey. And with this - you can use multiple keys and users on the same host without too much trouble \ud83d\ude42<\/p>\n
Another example with different ssh port:<\/p>\n
Host myHost2\n Hostname myhost.com\n Port 3001\n User anotheruser\n IdentityFile ~\/.ssh\/anotherKey<\/pre>\nYou can also just give your ssh connection another keyfile:<\/p>\n
Host github.com\n IdentityFile ~\/.ssh\/github<\/pre>\nForward a local port from your remote pc to yours:<\/p>\n
Host myHost_tunnel\n Hostname myhost.com\n IdentityFile ~\/.ssh\/myHostKey\n User myUser\n LocalForward 443 127.0.0.1:443<\/pre>\nOr even use your remote host as HTTP proxy (binding on your local port 8888):<\/p>\n
Host myHost_proxy\n Hostname myhost.com\n IdentityFile ~\/.ssh\/myHostKey\n User myUser\n DynamicForward 127.0.0.1:8888<\/pre>\nAnd the ssh config is even able to do a lot more but ... you'll find that in the manpage of ssh \ud83d\ude42<\/p>\n