Post-Quantum Rosenpass Dual-KEM WireGuard Mesh
Defend critical site-to-site and SD-Branch tunnels against Harvest Now, Decrypt Later (HNDL) quantum adversaries. Axonwall's rosenpass plugin pairs user-space Classic McEliece 460896 (code-based KEM) and ML-KEM-512 (Kyber-512) (lattice-based KEM) with the ultra-fast in-kernel Linux WireGuard data plane.
1. Why Classical X25519 Needs a Dual-KEM Upgrade
Standard WireGuard uses the Noise_IKpsk2 handshake over Curve25519 (ECDHE) and encrypts transport packets with ChaCha20-Poly1305. While symmetric 256-bit ChaCha20 remains resistant to Grover's quantum search algorithm, X25519 elliptic-curve key agreement is vulnerable to Shor's algorithm on a Cryptographically Relevant Quantum Computer (CRQC).
By feeding a continuously rotated 256-bit Post-Quantum Pre-Shared Key (PSK) derived from two orthogonal mathematical families—Classic McEliece 460896 (Goppa codes) and ML-KEM-512 (Kyber-512) (Module-LWE lattices)—directly into the kernel WireGuard interface every 120 seconds (via anonymous in-RAM memfdSecret descriptors so ephemeral PSKs never touch disk), Axonwall achieves post-quantum forward secrecy and fail-closed boot protection (failClosedBootGuard: true) without sacrificing a single megabit of in-kernel WireGuard throughput.
+-------------------------------------------------------------------------+
| USERSPACE CONTROL PLANE: rosenpass daemon (UDP :9999) |
| • Classic McEliece 460896 (Code-Based KEM — 524 KB Static Public Key) |
| • ML-KEM-512 / Kyber-512 (Lattice-Based Ephemeral KEM) |
| • Blake2b Key Derivation -> Rotates 256-bit PSK every 120s (memfd) |
+------------------------------------+------------------------------------+
| wg set wg0 peer <PUB> preshared-key
v
+-------------------------------------------------------------------------+
| LINUX KERNEL DATA PLANE: wireguard.ko (UDP :51820) |
| • Noise_IKpsk2 (X25519 + Rosenpass PQ-PSK, fail-closed boot guard) |
| • ChaCha20-Poly1305 SIMD / AVX-512 Wire-Speed Packet Encryption |
+-------------------------------------------------------------------------+2. Configuring Post-Quantum Rosenpass Peers
Enable the rosenpass plugin via sudo axonwallctl plugin enable rosenpass (or in /system/plugins), then declare your Rosenpass listener and peers under rosenpass: inside /etc/axonwall/vpn.yaml:
rosenpass:
enabled: true
listenPort: 9999
listenAddresses:
- 0.0.0.0:9999
wgDevice: wg0
verbosity: Quiet
rekeyIntervalSeconds: 120
failClosedBootGuard: true
memfdSecret: true
publicKeyPath: /etc/rosenpass/pq.pk
secretKeyPath: /etc/rosenpass/pq.sk
peers:
- name: hq-zurich-core01
wgPeerPublicKey: 7xK9pL2mN4qR8sT1vW3xY5zA7bC9dE1fG3hJ5kL7mN0=
endpoint: 198.51.100.10:9999
pqPublicKeyPath: /etc/rosenpass/peers/hq-zurich-core01.pq.pk- Web Console: Navigate to /vpn/rosenpass to generate Classic McEliece 460896 + ML-KEM-512 keypairs, export peer public keys, and monitor live PSK rotation epochs.
- Neovim Super Configurator & Standalone TUI: Run
axonwall-config vpnto edit/etc/axonwall/vpn.yaml, or launchaxonwall-tuiand open Tab[5] Services & PQ(press[g]for PQ keypair generation). - CLI Verification: Run
sudo systemctl status axonwall-rosenpassandsudo wg show wg0to confirm activepreshared key: (hidden)injection.