Post-quantum keys that roll.
The tunnel’s keys are agreed with a post-quantum exchange, with no classical-only fallback. Then they are replaced every 2 minutes, or every gigabyte.
Every deviceYour serverAlways on
Ten minutes of one session
What happens
- Your device and your server agree keys with X25519MLKEM768. A classical exchange and a post-quantum one together, so both would have to be broken.
- There is no classical-only fallback. TLS 1.3 only, inside QUIC, with no resumption.
- Each end proves itself with keys the other already knows. No certificate authority is asked: your device knows your server’s keys, and your server knows each device’s.
- Traffic keys are replaced every 2 minutes or every gigabyte, whichever comes first.
- Your traffic is sealed with ChaCha20-Poly1305 or AES-256-GCM. Whichever your processor runs faster.
What it costs
A larger first exchange, and steady work for your processor.
- Connecting
- A post-quantum exchange sends larger keys than a classical one, so the first packets of a session are bigger. It happens once a session.
- Your processor
- Every packet is sealed on your device and opened on your server. On a small router, that work can set the ceiling before the links do.
- Data
- A few bytes on every packet, for the seal.
- Choice
- None. There is no weaker setting to fall back to, and nothing to tune.
Turn it on
There is nothing to turn on, and nothing to turn off. These show it, and look after your server’s own keys.
| To | Command line | Router UI, app and console |
|---|---|---|
| See the tunnel, and what it runs over | fenris status | Home |
| Check each step to your server | fenris check | Diagnostics |
| Make a new server key now | fenris-server rotate --state /var/lib/fenris-server | The console, Keys & backup |
| Keep the root key off the server | fenris-server root export --state /var/lib/fenris-server --to <file> --remove | The console, Keys & backup |
Where to find it
The consoleAudit log. Each session, each sign-in, and each attempt the server refused.
The appHome. Protected, through your server.
The consoleAdd a device. Each device makes its own keys as it joins.
The productThree of its own screens, with example data.
What it keeps
No traffic keys. They live in memory, and each is thrown away as it is replaced. Your server keeps each device’s public keys, so the device can connect. A device’s own keys never leave it.
Where it stops
- To your server
- It is encrypted from your device to your server. Past it, your traffic is as protected as the website makes it.
- A key update
- Every 2 minutes the traffic keys move on from the last ones. It is an update inside the session, not a fresh exchange.
- Where UDP is blocked
- A path that runs as TLS on TCP 443 has an outer layer of TLS that also accepts a classical exchange.
- How it is checked
- Conformance tests cover this profile, and formal models cover enrolment and the proof a silent server asks for. There has been no outside audit.