Post-Quantum VPN
QuicN
The QUIC-based Post-Quantum VPN protocol that enables the Cosineq architecture. High performance and small enough to live in a container.
QuicN is the protocol that drives Cosineq, designed and developed by Cosinium. Based on QUIC and TLS 1.3, with mandatory post-quantum key exchange at every point in the architecture, including on networks that choose a classical identity algorithm.
Algorithms
| Role | Algorithm | Notes |
|---|---|---|
| Key exchange, every handshake | X25519MLKEM768 | Mandatory post-quantum hybrid X25519 + ML-KEM-768 (FIPS 203). |
| Identity signature, default | ML-DSA-44 | Self-created X.509, pinned by the SHA-256 of its SubjectPublicKeyInfo (SPKI). No CA and no chain in the certificate. |
| Identity signature, opt-in | Ed25519 | A classical algorithm you can choose for your network, but only deliberately, because it is not post-quantum safe. Available for interoperability or low-power devices. |
| Control-plane trust root | ML-DSA-44 | Always enforced on controllers, relays, and STUN servers. |
| Data plane | AES-256-GCM | Only two TLS 1.3 cipher suites are accepted. AES is chosen because any reasonable device has built-in hardware instructions that make it fast and efficient. |
Session confidentiality post-quantum everywhere with hybrid key exchange as a mandatory on every network. Ed25519 is offered any only for relaxingpeer identity authentication, but the trust root stays post-quantum regardless.
How a connection actually gets made
In every case the encrypted overlay is a layer riding over the network you already have. These diagrams show it as a session floating above the physical path.
Why it is fast
without a kernel changes, DPDK, hugepages, or dedicated cores.
- Minimising OS system calls and carrying dozens of packets
- Uses all the network packet offloads available to userspace from the kernel to move as many packets across the network stack as efficiently as possible.
- Tuned algorithms to attain crypto performance
- Efficiently processes packets without eating up all CPU resources. The choices of algorithms is intended to keep the other CPU cores available for system use. Memory usage is also tuned to match the host platform so that it stays flat while transferring at high speed, even when under pressure.
Capabilities built into the protocol
- Access control on every packet
- A per-peer filter enforced on both inbound and outbound traffic: anti-spoofing, outbound masquerading, connections to destination services.
- Secure STUN
- Unlike RFC 5389, the client's message is is encrypted under both ways.
- TLS-shielded Relay
- Pass packets through a relay that wraps them in TLS to appear as HTTPS traffic.
- A lightweight protocol specification
- Because it's UDP QUIC. Three easily parsable control messages on one stream, and everything else is transmitted across a single format data-plane.
quicn-rs: a community edition implementation
quicn-rs is a minimal peer-to-peer build of the protocol in Rust that works on Linux, macOS and Windows. We developed it to show that the protocol is open and to act as an independent conformance check against our high-performance reference implementation. Stay tuned - we'll be sharing it in our public git repository.