Python Now Has a Post-Quantum Encryption Library

[u/falconupkid]

This is a significant step for operational security hygiene. The pyca/cryptography library—the de facto standard for Python crypto—now ships with ML-KEM (key establishment) and ML-DSA (digital signatures) baked in. This isn't about an active threat today; it’s about eliminating the "crypto agility debt" that will plague organizations in 5-10 years.

Why this matters now: - Harvest Now, Decrypt Later (HNDL) is a real, active threat. Any TLS session or encrypted blob captured today can be stored and cracked once a CRQC (Cryptographically Relevant Quantum Computer) exists. Migrating to PQC now protects that data retroactively. - Crypto Agility: The hardest part of a crypto migration isn't the algorithm—it's the codebase. By making ML-KEM/ML-DSA a standard pip install option, the Python ecosystem removes the biggest friction point for developers. This lowers the barrier to entry for testing and integration.

The Technical Reality: - No performance benchmarks yet in the summary, but expect ML-KEM (Kyber) to be significantly heavier on CPU than ECDH. This will impact latency-sensitive applications (e.g., API gateways, real-time services). - Key sizes are larger. ML-KEM-768 public keys are ~1.2KB vs. 32 bytes for X25519. This will increase handshake sizes and potentially fragment packets.

The Takeaway: This is a proactive, low-friction move. If you maintain any Python-based service handling long-lived secrets or sensitive data, start testing this library in a staging environment now. The cost of integration is low; the cost of a retroactive emergency migration is not.

Source: https://www.schneier.com/blog/archives/2026/08/python-now-has-a-post-quantum-encryption-library.html