Skip to content

Post-Quantum SSH on iPhone: What ML-KEM Negotiation Actually Requires

Understand hybrid ML-KEM SSH key exchange and verify both client and server support before calling an iPhone SSH session post-quantum protected.

1 min readNeoServer

Post-quantum SSH protection is a property of the negotiated connection, not just a feature listed for one endpoint. The hybrid mlkem768x25519-sha256 exchange combines ML-KEM with classical X25519. NIST standardized ML-KEM in FIPS 203, and OpenSSH documents the hybrid exchange.

Check both ends of the SSH connection

The client and server must both offer a compatible hybrid key exchange, and their configurations must allow it. OpenSSH 9.9 introduced mlkem768x25519-sha256; OpenSSH 10.0 made it the default preference. An older server or custom policy may negotiate a different method.

On a trusted desktop, ssh -Q kex lists algorithms supported by that local client; it does not prove what a remote server offers or what an iPhone app negotiated. A verbose desktop connection, ssh -vv user@host, can show the negotiated kex: algorithm for that desktop session. It still does not establish the algorithm used by NeoServer on iPhone.

What can you conclude about NeoServer?

NeoServer connects to SSH servers, but this website currently has no verified client-handshake result or in-app algorithm display establishing ML-KEM negotiation for its iPhone connection. Therefore, do not assume that an SSH session in NeoServer used ML-KEM solely because the server supports it. Confirm with a trustworthy client-side diagnostic or a product release note that identifies the negotiated method before making that claim.

Hybrid key exchange addresses future attacks against recorded session-key establishment. It does not replace host-key verification, account security, software updates, or careful handling of private keys. For SSH setup, see the NeoServer user guide.

Ready to try it?

NeoServer · SSH, Mosh, Docker & SFTP client for iPhone, iPad and Mac

Free on the App Store