Networking, Unix

[Series] SSH for Developers – Beyond the Basics

I have written this guide for developers who might be superficially familiar with the basics of SSH – maybe even fiddled with a file or two without really knowing what’s going on – and would like a more cohesive overview of its most powerful features.

This is essentially an organised collection of the main gotchas and topics that gave me (a dev, not a sysadmin) the most dexterity in jumping about from machine to machine in the cloud.
It is meant to be read in succession as each topic builds on the previous, but I also tried to keep them loosely coupled in case the reader is only interested in a particular section.

Have fun.

Table of Contents:

  1. Authentication
  2. Known Hosts
  3. SSH Agent
  4. Config
  5. Jumping Hosts
  6. Tunnelling and Port Forwarding
  7. X11 Forwarding
  8. Multiplexing and Master Mode

Disclaimer: This does not mean to be a complete list of all that is possible with SSH. That would probably take a book. Or two. But any feedback about additions is welcome.

First, a refresher. What is SSH?

SSH is a protocol built on top of TCP that is intended to provide a secure channel for a client and a server to communicate. In its implementation, it consists of two programs:

  • An SSH client
  • An SSH daemon on the server that accepts connections, typically on port 22

Both client program and daemon are commonly pre-installed on most modern Unix-like operating systems.
Other little helper tools like ssh-keygen, ssh-agent and ssh-add are also part of the family of SSH executables.

SSH was originally designed as a replacement for Telnet and older, unsecured remote shell protocols. The encryption used by SSH is intended to provide confidentiality and integrity of data over unsecured networks, such as the Internet. Fun fact: it was developed by a fucked off engineer in response to a password sniffing attack on a university network.

This kind of security is typically thought of as necessary to log into a remote machine and execute commands here and there, but SSH also supports many other advanced use cases such as tunnelling, forwarding TCP ports, transferring files, X11 forwarding, etc. which we’ll see later.

First, let’s make sure we properly cover the main feature and selling point of SSH: authentication.

Next: Authentication →

Resources and Further Reading

Leave a Reply