What Actually Happens When You Type ssh host uptime? 🖥️

Typing a simple command like $ ssh host uptime feels instant, but there is a massive amount of cryptographic heavy lifting happening under the hood.

This sequence diagram perfectly breaks down the 19 steps that happen in the milliseconds after you hit enter. Whether you are deploying an Airflow pipeline, configuring remote Docker containers, or spinning up an MCP server, SSH is the backbone of backend infrastructure.

Here is what is actually happening:

1️⃣ The Handshake & Key Exchange (Steps 1-7): It starts with a TCP connection on port 22. Both sides negotiate algorithms and exchange ephemeral keys to compute session keys. From step 7 onward, the connection goes dark and everything is fully encrypted.

2️⃣ Authentication (Steps 8-13): The client checks the host key against ~/.ssh/known_hosts. Then, it asks to use a key, the server checks ~/.ssh/authorized_keys, and the client's private key signs the request without ever leaving the client machine.

3️⃣ Execution & Teardown (Steps 14-19): Once logged in, a session is opened, the command (exec "uptime") runs, and the server returns the output and an exit status code before safely closing the connection.

Understanding this lifecycle is crucial for debugging deployment issues, securing automated pipelines, or setting up secure remote environments.

What is your favorite terminal command that hides this level of complexity? 👇