Post-Quantum Cryptography Explained

Every secure website, encrypted message, and digital signature relies on public-key cryptography. But quantum computing will break these algorithms. This article explains why, what NIST has standardized as replacements, and what developers should do now.

Why Quantum Computing Breaks Current Crypto

Current public-key cryptography relies on mathematical problems that are computationally hard for classical computers. Shor's algorithm (1994) proved that quantum computers can solve these problems efficiently:

The Harvest Now, Decrypt Later Threat

The most urgent reason to migrate is not that quantum computers exist today -- they do not. The threat is "harvest now, decrypt later":

• Today: Adversaries collect encrypted traffic and store it
• Future: When quantum computers arrive, they decrypt the stored data
• Impact: Secrets, credentials, and sensitive data become exposed

Data that must remain secret for 10+ years (medical records, government secrets, financial data) is already at risk. The encryption protecting it today will be broken tomorrow.

NIST Post-Quantum Cryptography Standards

On August 13, 2024, NIST finalized three post-quantum cryptography standards:

Additional algorithms in development:

• FN-DSA (Falcon): Compact signatures, expected standardization 2027
• HQC: Code-based KEM, backup for ML-KEM

ML-KEM: Key Encapsulation (FIPS 203)

ML-KEM (Module Learning With Errors Key Encapsulation Mechanism) replaces RSA and ECDH for key exchange:

# ML-KEM-768 key encapsulation
import oqs

# Generate keypair
kem = oqs.KeyEncapsulation('ML-KEM-768')
pk = kem.generate_keypair()      # 1,184 bytes (public key)
sk = kem.export_secret_key()     # 2,400 bytes (secret key)

# Encapsulate (Bob)
ct, ss = kem.encap_secret(pk)    # ct = ciphertext, ss = shared secret

# Decapsulate (Alice)
ss2 = kem.decap_secret(ct, sk)   # ss2 == ss (same shared secret)

ML-DSA: Digital Signatures (FIPS 204)

ML-DSA (Module Digital Signature Algorithm) replaces RSA and ECDSA for signatures:

# ML-DSA-65 digital signatures
sig = oqs.Signature('ML-DSA-65')
pk = sig.generate_keypair()      # 1,952 bytes

message = b'Important document'
signature = sig.sign(message)    # ~3,293 bytes

# Verify
valid = sig.verify(message, signature, pk)  # True

Key Size Tradeoff

The main practical difference: PQC keys are significantly larger.

ML-KEM public keys are ~5x larger than RSA. ML-DSA signatures are ~13x larger. This is acceptable for most applications but requires testing in bandwidth-constrained environments.

Migration Timeline

What Developers Should Do Now

1. Inventory cryptographic usage -- Find all RSA, ECC, and DH in your systems
2. Classify data by sensitivity -- What must stay secret for 10+ years?
3. Test PQC in non-production -- Use liboqs, AWS KMS, or Cloudflare PQC
4. Start with new systems -- Use PQC-first for new deployments
5. Plan migration timeline -- Prioritize long-lived secrets
6. Monitor NIST updates -- FN-DSA and HQC may become additional standards

Try It Yourself

• AES Key Generator -- Generate quantum-safe symmetric keys
• Secure Random Token Generator -- Generate cryptographically secure tokens
• Hashing vs Encryption vs Encoding -- Understand cryptographic primitives

Related BestWordz Articles

• Quantum Computing for Software Developers -- Why quantum threatens crypto
• Qubits vs Classical Bits -- Quantum fundamentals
• How HTTPS and TLS Actually Work -- TLS handshake (PQC will replace this)
• Hashing vs Encryption vs Encoding -- Crypto concepts
• Secrets Management for Developers -- Protecting secrets
• API Authentication Methods -- Auth mechanisms

Summary

Post-quantum cryptography is not theoretical -- the standards are finalized and ready for implementation:

1. Shor's algorithm breaks RSA, ECC, and Diffie-Hellman
2. ML-KEM (FIPS 203) replaces RSA/ECDH for key exchange
3. ML-DSA (FIPS 204) replaces RSA/ECDSA for signatures
4. SLH-DSA (FIPS 205) provides conservative hash-based signatures
5. Symmetric crypto (AES, SHA) is quantum-safe with standard key sizes
6. Start migration now -- harvest now, decrypt later attacks are real

Further Reading

• NIST Post-Quantum Cryptography
• NIST PQC Standards Announcement
• Open Quantum Safe (liboqs)
• Cloudflare: NIST PQC Standards

NIST standards verified: FIPS 203, 204, 205 (August 13, 2024). Migration timeline from NIST IR 8547.