releases
VPN Works 0.10.0 Signs Every Ledger Checkpoint With a Key No Plugin Can Read
VPN Works 0.10.0 signs the Ledger. The kernel holds a key, one per machine, and signs each checkpoint and the end of a run’s sealed record. Ledger never sees the …
releases
VPN Works 0.10.0 signs the Ledger. The kernel holds a key, one per machine, and signs each checkpoint and the end of a run’s sealed record. Ledger never sees the …
releases
VPN Works 0.9.0 gives Guard plugins byte budgets. A Guard lets a connection through with a budget, and the kernel counts every byte, cuts the connection when the budget …
releases
VPN Works 0.7.0 brings Exit back, inside vpnw itself. vpnw exit runs on a server with fixed addresses, takes each client’s requests over TLS, decides every one …
releases
VPN Works 0.8.0 opens a new kind of plugin, the Tunnel. A Tunnel plugin hands the kernel WireGuard configs and says how long to keep each, and vpnw runs every tunnel …
releases
VPN Works 0.5.0 brings Ledger back, as plugins. One seals every event of a run into a file as it happens. The other checks that file and names the line anyone changed. …
releases
VPN Works 0.6.0 brings Lab back as the fault kit every tunnel must pass before it ships. It broke the WireGuard path 18 ways. The path now handles all 18, and four fixes …
testing
Every number on vpnw.com comes from one script in the code repository, run on one Linux machine with 2 CPUs. Its output is committed next to the code, so anyone can check …
releases
VPN Works 0.4.0 sends one program through a WireGuard tunnel and leaves the rest of the machine alone. vpnw runs the tunnel itself, inside its own process, so it needs no …
releases
VPN Works 0.4.1 adds no features. It closes the one gap the 0.4.0 tests left open, and it fixes a bug those same tests turned up along the way. The gap was IPv6. A sealed …
releases
VPN Works started as five separate engines that each worked and didn’t add up to one thing. Version 0.3.0 rebuilt it from scratch as one small core, vpnw, with …