After an eight-year public competition, NIST picked replacements built on math that quantum computers aren’t known to shortcut. You won’t implement them yourself. You’ll buy products that do, so it helps to know the names on the spec sheet.
How two computers agree on a secret key over the internet. The one to prioritize, because it protects against harvest-now attacks.
The main general-purpose signature: proves a website, software update or document is genuine.
A conservative backup built only on hash functions. Larger and slower, but rests on very well-understood math.
Compact signatures for places where size matters, like certificates and constrained devices.
A backup to ML-KEM built on different math (error-correcting codes), in case lattices ever show a weakness.
Post-quantum keys and signatures are much larger. That’s why old firewalls, VPNs and embedded devices sometimes choke on them, and why testing matters.
Bytes. ML-KEM-768 and ML-DSA-65 are the common general-purpose settings. FN-DSA-512 signature size is an average. Linear scale within each group.
Most systems won’t switch overnight. They run the old and new algorithms together and combine the results, so an attacker has to break both. This is already the default in Chrome and is supported by OpenSSL 3.5 and later.
When you buy or renew a VPN, firewall, identity provider or hosting plan, ask for FIPS 203 (ML-KEM) support by name, and whether the product can switch algorithms with a software update.