What Is SSH? OpenSSH 10.6 & Post-Quantum Security

SSH (Secure Shell) is the encrypted protocol that lets you log in to a remote computer and run commands as if you were sitting in front of it. It replaced older tools like Telnet because it encrypts everything — your password, your commands, and the results. OpenSSH 10.6, released on October 6, 2026, is the latest version of the world’s most popular SSH software: it enables a post-quantum signature algorithm, warns server admins about weak cryptography, and deliberately disables two risky features to keep connections safer. In this guide, we break down ssh openssh post quantum in plain English — what it is, how it works, and how to use it.

Definition: SSH (Secure Shell) is a cryptographic network protocol for operating network services securely over an unsecured network. Its best-known use is secure remote login, but it also powers encrypted file transfers (SFTP, SCP), secure tunnels, and automated deployments. (Wikipedia)

Ssh Openssh Post Quantum: What is SSH in simple terms?

Imagine your website’s server lives in a data center hundreds of miles away and something breaks. SSH is the secure remote control that gets you there: you open a terminal, type ssh user@example.com, and you get a command line on that distant machine — with everything encrypted so nobody on the network can read it.

SSH was born in 1995, when Finnish researcher Tatu Ylönen at the Helsinki University of Technology designed it after a password-sniffing attack hit his university network. The tools of the day — Telnet, rlogin, FTP — sent usernames and passwords as plain, readable text, so SSH replaced them with strong authentication and encryption. He picked port 22 simply because it sat free between Telnet’s port 23 and FTP’s port 21; the improved SSH-2 protocol became an IETF internet standard in 2006. (Wikipedia)

How does SSH work?

SSH follows a client–server model: your computer runs the client, the remote machine runs the server (sshd) on TCP port 22. Connecting takes seconds and three steps:

1. Handshake: client and server agree on which encryption algorithms to use — this negotiation is called key exchange.
2. Server check: the server proves its identity with a host key, so you know you’re not talking to an impostor.
3. Encrypted session: everything from then on is encrypted with fast symmetric ciphers like AES or ChaCha20, with integrity checks verifying nothing was tampered with.

Asymmetric crypto (key pairs) sets up the connection and proves identity; symmetric crypto carries the conversation at speed.

What are SSH keys?

Instead of a password, you prove identity with a key pair: a private key that never leaves your computer and a public key on the server. Keys are far harder to steal or guess than passwords, so many servers disable password login entirely. Create one with: ssh-keygen -t ed25519.

What is OpenSSH?

OpenSSH is the world’s most widely used SSH software: a free, open-source implementation by the OpenBSD developers, first released in 1999. (Wikipedia) It ships by default on Linux, macOS, and most servers (and runs on Windows too). “SSH into the server” almost always means OpenSSH’s ssh client talking to its sshd server — the daily tool for deploying code, managing cloud machines, and pulling from Git, including into containers (see What Is Kubernetes? Containers Explained for Business).

What’s new in OpenSSH 10.6?

OpenSSH 10.6 arrived on October 6, 2026, with the project promising more frequent releases — a wave of security reports, many found with AI assistance, is turning up bugs faster than the old schedule could ship. (Linuxiac) Headline changes:

• Post-quantum signatures enabled: the hybrid signature algorithm ssh-mldsa44-ed25519 is now switched on. Keys made with the earlier experimental @openssh.com version should be regenerated or removed. (Help Net Security)
• Server-side weak-crypto warnings: sshd now enables WarnWeakCrypto by default, logging every connection that doesn’t use a post-quantum-safe key exchange.
• Compression deliberately weakened: the LZ77 dictionary coder used by SSH compression is disabled, closing a side-channel (“Crossing the Streams” research) where shared compression state could leak secrets between channels. Compression still works but less effectively; the project recommends application-level compression instead. (Zot News)
• Stricter usernames: ssh now refuses command-line usernames containing $ or \, blocking shell-injection via ProxyCommand or Match exec. This affects Windows/AD shops logging in as CORP\alice; names set via the User config directive are exempt. (Help Net Security)
• Deprecations: scp -R (remote-to-remote copies) still works but warns and will be ignored in a future release. SFTP gains mkdir -p; private-key encryption now uses 32 KDF rounds instead of 24.

Encryption standards keep tightening everywhere — even TLS certificates are on a shrinking lifetime (see Why SSL Certificates Are Shrinking to 64 Days).

What does “post-quantum” mean in SSH?

Today’s SSH key exchange relies on math that classical computers can’t practically crack — but a sufficiently powerful quantum computer could. No such machine exists yet; estimates range from 5–20 years, many expecting the mid-2030s. (openssh.com)

The catch is the “store now, decrypt later” attack: an adversary can record your encrypted sessions today and decrypt them years from now once quantum hardware arrives. Traffic you send now is only safe if the key exchange is quantum-resistant.

OpenSSH’s answer is hybrid post-quantum key exchange: it combines the NIST-standardized ML-KEM algorithm with the classical X25519 exchange, mixing both secrets — so the connection is no worse than the old crypto even if the new algorithm ever proves flawed. (openssh.com) Here’s how OpenSSH got here:

One honest caveat: so far this protects the key exchange (the tunnel). Your login keys (RSA, ECDSA, Ed25519) are still classical — post-quantum authentication is still to come. (openssh.com) Major providers are moving the same way: GitHub has enabled hybrid post-quantum key exchange on its SSH endpoints. (DevOps Daily)

SSH vs. the old way: why it replaced Telnet

How can I make my SSH connections quantum-ready?

If both ends are reasonably up to date, you’re probably already using post-quantum key exchange. Verify and tighten up:

1. Upgrade both sides. Install a recent OpenSSH (10.x) on your laptop and your servers — the server side matters most, since old servers can’t offer the new algorithms.
2. See what your connection uses. Run ssh -v user@host 2>&1 | grep "kex: algorithm" — look for mlkem768x25519-sha256. (The same check verifies providers like GitHub. DevOps Daily)
3. Audit your server. sshd -T | grep kexalgorithms should list mlkem768x25519-sha256 near the front; 10.6’s WarnWeakCrypto also logs weak connections automatically.
4. Use modern keys. Generate Ed25519 keys (ssh-keygen -t ed25519), retire old DSA keys (removed in OpenSSH 10.0), and consider disabling password authentication.
5. Regenerate experimental PQ keys. Keys made with the early @openssh.com experimental format should be replaced with the finalized ssh-mldsa44-ed25519.
6. Don’t silence warnings blindly. If your client warns a connection isn’t post-quantum, the real fix is upgrading the server — silencing it per-host accepts the risk rather than removing it. (openssh.com)

Whether you’re pushing code or deploying a backend like Supabase Explained: The Open-Source Firebase Alternative, these steps take minutes and future-proof years of traffic against “store now, decrypt later” collection.

Frequently asked questions

Is SSH the same as OpenSSH?

No. SSH is the protocol — the rules for secure remote communication. OpenSSH is the most popular software implementing it, built by the OpenBSD team.

What port does SSH use?

TCP port 22, assigned because it sat conveniently between Telnet (23) and FTP (21). You can run SSH on other ports, but 22 is the universal default. (Wikipedia)

Will a quantum computer break my SSH keys tomorrow?

No. No cryptographically relevant quantum computer exists yet, and estimates put one 5–20 years out. The real threat is “store now, decrypt later” — adversaries recording today’s encrypted sessions to decrypt later. Upgrading to post-quantum key exchange now closes that window. (openssh.com)

What should I do if SSH shows a post-quantum warning?

It means the server didn’t offer a post-quantum key exchange. The ideal fix is upgrading the server to OpenSSH 9.0+ (9.9+ for ML-KEM). You can silence the warning per-host with WarnWeakCrypto, but that accepts the risk rather than removing it. (openssh.com)

Do I need to upgrade to OpenSSH 10.6 right now?

If you run servers, plan it soon: you get post-quantum signatures, automatic weak-crypto logging, and security fixes. Test first — the disabled LZ77 compression, the $/\ username restriction (watch CORP\user logins), and the scp -R deprecation can surprise existing setups. (Linuxiac)