Patent-free · Pure Rust · Formally verified

SSH was designed in 1995.
qssh was designed for quantum adversaries.

A from-scratch post-quantum SSH replacement with 17 features OpenSSH doesn't have. Every critical component carries formal mathematical proofs of correctness — not tested, proven.

Request a Demo View on GitHub
117
Formal Proofs
156
Tests Passing
768
Byte Frames
0
Patents
0
Lines of C
Differentiators
What OpenSSH doesn't have.

17 capabilities that don't exist in OpenSSH at any configuration level. Not extensions — architectural differences.

1

Post-Quantum Signatures

OpenSSH uses RSA/ECDSA/Ed25519 — all broken by Shor's algorithm. qssh uses Falcon-512 (lattice-based, 666-byte signatures) and SPHINCS+ (hash-based, stateless) — both NIST-selected, both quantum-resistant.

2

Constant-Size 768-Byte Frames

Every packet on the wire is exactly 768 bytes. Data, keepalives, control messages — all identical size. OpenSSH leaks metadata through variable packet sizes (keystrokes vs file transfers are distinguishable). qssh frames are indistinguishable to network observers.

3

Hybrid Key Exchange (ML-KEM + X25519)

qssh combines ML-KEM-768 (post-quantum lattice KEM) with X25519 (classical ECC) — if either is broken, the other still protects the session. OpenSSH uses single-family ECDH only.

4

Quantum Random Number Generation

Pluggable quantum entropy from KIRQ Hub, Crypto4A HSM, or local /dev/qrandom devices — always mixed with OS entropy for defense in depth. OpenSSH uses OS RNG only.

5

QKD Integration (BB84 / E91 / ETSI-QKD-014)

Direct support for quantum key distribution protocols — information-theoretic security. OpenSSH has no QKD integration at all.

6

Security Tier System (T0–T5)

Six progressive security levels from classical compatibility through full hybrid quantum. OpenSSH has a single security model.

7

Traffic Obfuscation

Dummy frame injection (30% probability), encrypted timestamps and sequence numbers in frame headers, random padding fills all unused payload space, configurable stealth mode. OpenSSH leaks timing, packet count, and size metadata constantly.

8

Post-Quantum Certificates

Falcon-512 and SPHINCS+ signed certificates for both users and hosts — with serial numbers, principal constraints, validity periods, and revocation. OpenSSH certificates exist but use quantum-vulnerable RSA/ECDSA.

9

Three-Tier Formal Verification

30 Kani bounded model checking proofs, 20 Verus deductive proofs, and 67 Lean 4 mathematical theorems — zero sorries. OpenSSH has zero formal verification.

10

Double Ratchet Forward Secrecy

Signal-style ratcheting key derivation — compromising one session key doesn't decrypt past or future messages. OpenSSH lacks per-message forward secrecy.

11

Lamport One-Time Signatures

Emergency fallback using pure hash-based signatures (no number theory). If Falcon and SPHINCS+ are ever broken, Lamport OTS provides last-resort quantum resistance using only SHA-256.

12

Isolated Signing Service

Unix socket signing daemon with mlock(2) preventing key swap to disk, per-key rate limiting (60 signs/minute), JSONL audit log with SHA-256 hash chain, and Argon2id passphrase protection. OpenSSH's ssh-agent has none of these.

13

SHA3-Based Symmetric Cipher

AES-256 has reduced quantum security (~128 bits via Simon's algorithm). qssh uses SHA3-256 counter-mode stream cipher maintaining full 256-bit security against quantum adversaries.

14

P2P Mode (No Server Required)

Direct peer-to-peer connections with NAT traversal (STUN/TURN) — no sshd daemon needed. OpenSSH always requires a listening server.

15

Session Resumption

Encrypted session tickets for fast reconnection — designed for mobile networks where connections drop. OpenSSH recreates the full handshake on every disconnect.

16

Pure Rust — Zero C FFI

The entire crypto stack is pure Rust. No C reference implementations, no FFI, no segfaults, no memory corruption class. OpenSSH is C with decades of CVEs.

17

Quantum-Native Protocol Design

qssh does not speak the SSH wire protocol. This is intentional — SSH's variable-length records, plaintext version strings, and algorithm negotiation all leak metadata. qssh was designed post-quantum from scratch with no legacy constraints.

Every frame is 768 bytes. Every time.

Data, keepalives, control messages — all identical on the wire. Encrypted headers, encrypted sequence numbers, random padding. No metadata leakage.

17 B
Header
719 B
Payload + Padding
32 B
HMAC
Header: 8B sequence + 8B timestamp + 1B frame type (all encrypted) · Payload: 2B length + data + random padding · MAC: HMAC-SHA256
Comparison
OpenSSH vs qssh.

A direct comparison across the dimensions that matter for post-quantum readiness.

Feature OpenSSH qssh
Signatures RSA, ECDSA, Ed25519 Falcon-512, SPHINCS+
Key Exchange ECDH ML-KEM + X25519 hybrid
Frame Size Variable (leaks metadata) Constant 768 bytes
Quantum Entropy No QRNG + KIRQ + Crypto4A
QKD No BB84, E91, ETSI-QKD-014
Security Tiers One Six (T0–T5)
Formal Verification None 117 proofs (Kani + Verus + Lean 4)
Forward Secrecy Per-session only Per-message (Double Ratchet)
P2P Mode No Yes (NAT traversal)
Certificates RSA-signed Falcon / SPHINCS+ signed
Language C Pure Rust
Security Tiers
Six levels. One protocol.

Progressive security from classical compatibility to full quantum assurance. T2 is the default — post-quantum with constant-size frames out of the box.

T0 — Classical

Legacy Compatibility

RSA/ECDSA signatures for interop with classical systems. Deprecated — migration path only.
Variable frames · Classical algorithms · No quantum protection
T1 — Post-Quantum

Basic Quantum Resistance

PQ algorithms with variable-length frames. Quantum-safe key exchange and signatures.
Falcon-512 + SPHINCS+ · ML-KEM hybrid · Variable frames
T2 — Hardened PQ (Default)

Production Standard

Post-quantum algorithms with constant 768-byte frames. Traffic analysis resistant. The default for all new connections.
Fixed 768B frames · Dummy injection · Encrypted headers · Full PQ
T3 — Entropy-Enhanced

Quantum Entropy

T2 plus pluggable quantum random number generation. For high-assurance environments requiring hardware entropy sources.
QRNG integration · KIRQ Hub · Crypto4A HSM · /dev/qrandom
T4 — Quantum-Secured

QKD Integration

T3 plus quantum key distribution for information-theoretic security. Critical infrastructure grade.
BB84 · E91 · ETSI-QKD-014 · Information-theoretic security
T5 — Hybrid Quantum

Maximum Assurance

All quantum layers active simultaneously. Every component quantum-secured from entropy through transport.
Full stack quantum · All tiers combined · Maximum assurance
Not tested. Proven.

Three independent verification tiers — from bounded model checking to deductive proofs to pure mathematics. Zero sorries. Zero axiomatized results.

30
Kani
AWS
Bounded model checking harnesses proving panic-freedom, integer safety, and memory bounds across all critical paths.
20
Verus
Microsoft Research
Deductive proofs of functional correctness — KDF chain composition, handshake protocol invariants, KEM encapsulation via Z3 SMT solver.
67
Lean 4
Mathlib v4.27.0
Mathematical theorems across 6 proof files — ML-KEM prime field, Falcon NTT compatibility, SPHINCS+ security bounds, transport frame invariants, KDF entropy.

Ready for post-quantum SSH?

Patent-free. Formally verified. Deploying now.

Request a Demo View on GitHub