SSH as a protocol, not a shell

If you only use SSH to get a terminal, you're missing the more interesting half. A tour of port forwards, multiplexing, and using SSH as glue.

If you only use SSH to get a terminal, you are missing the more interesting half.

Beyond the shell

A tunnel. A socket. A file copy. A unix domain socket over the internet.

Multiplexing

ControlMaster will change the day you turn it on. Sessions in milliseconds.

Port forwards

Local, remote, dynamic. Three flags, three superpowers.

SSH as glue

For internal tools, SSH replaces a VPN, a jumpbox, and half a deployment system.

∎ thanks for reading. the rest of the archive is here.