Protocol Simulations / PQC SSH Simulator

What you will do: Pick a PQC KEX (hybrid or pure ML-KEM) and an ML-DSA or SLH-DSA host key, press Run comparison, then compare the classical curve25519 baseline with the PQC run in the Run Log, PKCS#11 Calls and Wire tabs.

Worked example: With the default mlkem768-curve25519-sha256 + ssh-mldsa-65 a real OpenSSH handshake runs: the log reports host and user C_Sign sizes and auth time, and the comparison bars show host pubkey, signature and KEX share bytes.

Runtime and privacy: The cryptographic exercise runs in this browser. Review the site privacy terms before entering sensitive material; use synthetic inputs for learning and evaluation.

Browse all Crypto Lab tools · Learn with VPN/IPsec & SSH

For your role

Developer / Engineer
Pick a key exchange such as mlkem768-curve25519-sha256 (marked REAL) and a host key like ssh-mldsa-65, press Run comparison, and read the Run Log, PKCS#11 Calls and Wire Packets tabs beside the classical baseline.
Security Architect
Compare the displayed algorithm identifiers, byte counts and timing for the classical and PQC samples. Check the retained result origin: a modeled operation trace does not measure network round trips or establish authentication. The Host Trust & TOFU note explains the host-key transition context.
Researcher / Academic
Inspect the retained result origin and operation log, then compare the reported signature and share byte counts across variants. Modeled packet entries illustrate a sequence; they are not captured network traffic or peer-verification results.

PQC SSH Simulator

Compare a genuine OpenSSH classical baseline with the selected PQC sample. Supported combinations run real OpenSSH; other combinations show modeled token operations and message sizes. The result panels identify the retained run type.

PQC KEX Algorithmhybrid = classical ECDH ⊕ ML-KEM; pure = ML-KEM only (CNSA 2.0)
PQC Host-Key Algorithmsofthsmv3 generates and signs with the chosen ML-DSA or SLH-DSA parameter set

Runs the bundled, modified OpenSSH binary. This Hub build adds experimental post-quantum signature names and softhsmv3 integration to OpenSSH 10.x; it is not an unmodified stock build. This combo drives its handshake compiled to WASM — both the host-key and user-key signatures are produced by C_Sign inside the embedded softhsmv3 token. The private keys never leave the HSM. (Client and server run in one WASM process over an in-memory transport; all crypto and wire formats are real.)

SSH sample operations and handshake telemetry

Classical (ecdsa-nistp256 + curve25519)

Not executed — click the matching run button above.

PQC (ML-DSA-65 + ML-KEM-768 × X25519)

Not executed — click the matching run button above.

Migrating SSH to post-quantum cryptography replaces classical key exchange (ECDH / Curve25519) and signatures (ECDSA / Ed25519) with a NIST-standardised ML-KEM hybrid or pure KEX and ML-DSA (FIPS 204) or SLH-DSA (FIPS 205) signatures — run the classical and PQC handshakes above to see the exact byte-size deltas for your selected combo. Both operations are delegated to softhsmv3 via PKCS#11 v3.2 C_Sign, ensuring private key material never leaves the token boundary.

Click "Run comparison" to start.

Keys are generated for sample use. Reset clears run results; reset the sample token separately to remove keys generated by modeled runs.

Production Tool Capabilities & Verification Requirements

What this sample check establishes: Demonstrates SSHv2 post-quantum hybrid key exchange (`mlkem768x25519-sha256` / `sntrup761x25519-sha512`) and host/user key authentication.

Browser sandbox limitation (non-certification boundary): Executes in browser WASM without testing enterprise bastion jump-hosts, PAM modules, or hardware PIV/FIDO2 SSH agents.

What to require and test in your production tools:

  • OpenSSH 9.9+ (or equivalent enterprise SSH server) enforcing `mlkem768x25519-sha256` in `KexAlgorithms`.
  • SSH CA certificate issuance and host-key rotation playbooks transitioning toward PQC/hybrid host authentication.
  • Audit logging of negotiated SSH KEX algorithms across all production hosts to eliminate legacy `diffie-hellman-group14-sha1` usage.

Try it

  1. 1. Predict before you run it.
  2. 2. Run or change the tool above.
  3. 3. Explain what the result shows.

You select ssh-mldsa-65. What else must you check before treating the displayed telemetry as an executed SSH handshake?

The peer negotiates the expected hybrid SSH exchange. Its host key does not match the trusted key record. Which rollout decision follows?

Next step

Turn it into a plan: Hybrid Transition Planner

This tool practises the VPN/IPsec & SSH module, phase 5 (Pilots & Migration); Hybrid Transition Planner produces a deliverable of that phase.

Next in Protocol Simulations