01
◎
A web connection
When you visit a website
Today
Server proves its identity
X25519 or ECDH agrees a secret
AES encrypts the session
Hybrid
Keep the current certificate
Add ML-KEM to secret agreement
AES still encrypts the session
Post-quantum
ML-DSA proves identity
ML-KEM agrees a secret
AES still encrypts the session
THE POINT
The public-key handshake changes. The fast encryption protecting the page stays.
02
↓
A software update
When a device installs code
Today
SHA-256 fingerprints the package
ECDSA signs the release
Device verifies the publisher
Hybrid
Keep the existing signature
Add an ML-DSA signature
Device checks both signatures
Post-quantum
SHA-256 fingerprints the package
ML-DSA signs the release
Device verifies the publisher
THE POINT
Code signing is about trust, not secrecy. The signature is the piece that evolves.
03
□
A long-term archive
When a document must stay private
Today
Create a random file key
AES-256 encrypts the document
RSA protects the small file key
Hybrid
AES-256 keeps protecting the file
Protect the file key twice
Use RSA and ML-KEM together
Post-quantum
Create a random file key
AES-256 encrypts the document
ML-KEM protects the file key
THE POINT
The document encryption remains familiar. It is the wrapped file key that must change.