Neo4j now supports post-quantum hybrid key exchange (X25519MLKEM768) for SSL/TLS encrypted Bolt connections, starting with the 2025.01 release. This addresses the 'Harvest Now, Decrypt Later' (HNDL) threat, where adversaries capture encrypted traffic today to decrypt it once quantum computers become capable. The hybrid approach combines classical X25519 elliptic curve Diffie-Hellman with the NIST-standardized ML-KEM-768 post-quantum algorithm, ensuring connections remain secure as long as either component holds. The feature requires OpenSSL 3.5+ and the OpenSSL provider configuration in Neo4j Enterprise Edition. A Docker-based setup example is provided, along with verification steps using openssl s_client. Post-quantum certificate authentication (ML-DSA, Merkle Tree Certificates) is planned for a future release.

10m read timeFrom medium.com
Post cover image
Table of contents
The Problem: Encrypted Today, Decrypted TomorrowIntroducing Post-Quantum Hybrid Key Exchange in Neo4jWhy OpenSSL 3.5+ Is RequiredWhat Neo4j Supports TodayGet Ian McCloy’s stories in your inboxCurrent Scope: Bolt FirstWhy This Protects Against HNDLWhat About Post-Quantum Certificates?Why Certificates Are a Later StepGetting Started
364 Impressions