Measure the cost of transitioning to post-quantum key exchanges.
Project details
The PQC Migration Benchmark project evaluates the performance of classical and post-quantum key exchange protocols, including hybrid options. By running real handshakes over TCP sockets, it provides insights into the latency and bandwidth implications of migrating to NIST's post-quantum cryptography standards, addressing critical security needs for the future.
The PQC Migration Benchmark project provides a comprehensive performance analysis of key exchange protocols, specifically comparing classical ECDH (X25519), post-quantum ML-KEM (FIPS 203 / Kyber), hybrid X25519+ML-KEM, and ML-DSA-signed ML-KEM key exchange methods. This benchmarking framework operates a real handshake over TCP sockets, leveraging liboqs alongside Python's cryptography library.
As the landscape of cryptography evolves, particularly with NIST recently finalizing post-quantum cryptography standards, understanding how these protocols perform is critical. The threat posed by potential quantum computers is not merely theoretical; adversaries could harvest encrypted data today and decrypt it in the future. This reality underscores the necessity for a seamless transition to hybrid key exchange methods that merge classical and post-quantum techniques. Most organizations are currently adopting this approach to enhance security as it requires both key primitives to be compromised to lose confidentiality.
The project aims to measure the costs associated with migrating from classical key exchange methods to hybrid and post-quantum approaches, focusing on handshake latency and the amount of data transmitted. The benchmarking methodology is distilled to specific modes, bypassing the complexity of a full TLS 1.3 implementation.
Here are the four modes measured:
| Mode | Protects | Server → Client | Client → Server |
|---|---|---|---|
| classical | Confidentiality only | X25519 pubkey | X25519 pubkey |
| pqc | Confidentiality only | ML-KEM pubkey | ML-KEM ciphertext |
| hybrid | Confidentiality only | X25519 pubkey ‖ ML-KEM pubkey | X25519 pubkey ‖ ML-KEM ciphertext |
| signed | Confidentiality and authenticity | ML-DSA pubkey, then ML-KEM pubkey ‖ ML-DSA signature | ML-KEM ciphertext |
Each handshake undergoes several assessments:
The project outlines significant findings on the performance impacts of different key exchange protocols:
For organizations considering the transition to post-quantum cryptography, what this project unveils is critical: while hybrid solutions mitigate risk effectively, the associated costs—both in terms of bandwidth and latency—need consideration in deployment planning. Further exploration is planned in developing a complete TLS 1.3 handshake to better align these benchmarks with real-world cryptographic applications.
Detailed results and graphs from all benchmarking runs can be found in the results/ directory, which contains insights from comprehensive trials conducted across various configurations.
Comments
0Start the conversation
Share the first comment.