Post-quantum VPN
Harvest Now, Decrypt Later: What a Post-Quantum VPN Can Protect
Quick answer
A harvest-now-decrypt-later attacker records encrypted traffic and hopes to recover it when future cryptanalysis becomes practical. Hybrid key agreement is intended to help protect newly established sessions against that risk. A VPN protects a defined client-to-server path; it does not retroactively upgrade old captures or secure every endpoint and destination.
Why confidentiality lifetime matters
Some information loses value quickly. Other information, such as research, business plans or private correspondence, can remain sensitive for years. Its confidentiality lifetime may extend beyond the period in which today's public-key techniques are expected to remain suitable.
An attacker does not need to decrypt a capture immediately for collecting it to be worthwhile. This is why migration can matter before a cryptographically relevant quantum computer exists. The date of such a capability remains uncertain; a security decision should consider exposure and data lifetime rather than a promised deadline.
What changes with a hybrid VPN handshake
ALightVPN's current release uses SecP384r1MLKEM1024. Its post-quantum contribution is intended to retain confidentiality if future attackers can defeat the classical contribution, subject to the construction's assumptions and a correct implementation.
That claim concerns the established key material. Correct identity validation, fresh randomness and secure handling of keys still matter. Frequent rekeying can limit use of an individual key, but it does not by itself turn a conventional key agreement into a post-quantum one.
Follow the protection boundary
| Exposure | Practical consideration |
|---|---|
| Traffic recorded between your device and the VPN server | Hybrid tunnel key agreement addresses future attacks on that exchange when correctly negotiated and implemented. |
| Traffic between the VPN exit and a website | Use HTTPS and evaluate the destination connection independently. |
| A compromised device or stolen session token | Endpoint and account protections remain necessary; a tunnel cannot repair a compromised endpoint. |
| A previously recorded conventional VPN session | A later client update does not change the keys or algorithms used by that old session. |
A VPN also does not erase identifying account logins or stop a destination from retaining data you submit. Choose it as part of a broader confidentiality plan.
A practical next step
Identify which information needs long-lived confidentiality, install a supported current client and verify the tunnel's negotiated group. Keep browsers and applications updated and continue using HTTPS. If your work belongs to an employer, follow its security policy before choosing a VPN.
Read how to verify the exchange and what a VPN protects for checks you can perform now. Business evaluations can use the migration checklist.
Common questions
Does an update protect traffic captured before the update?
No. Recorded sessions retain the security properties of the algorithms, keys and configuration used when they were established.
Should I continue using HTTPS through a VPN?
Yes. The VPN tunnel ends at its server; HTTPS protects the separate application connection to the destination.
Does post-quantum key exchange guarantee future confidentiality?
No absolute guarantee follows. Protection depends on cryptographic assumptions, implementation, authentication, endpoints and the actual negotiated session.
Sources and product references
- NIST: preparing for post-quantum cryptography
- RFC 10024: hybrid key agreement for TLS 1.3
- Official ALightVPN downloads
Reviewed 2 November 2026. Release configuration and platform availability are distinct from live-session test evidence.