Rosetun

WINDOWS LINUX OPEN SOURCE

Protection guarantees

Stable release: 0.6.0 · Windows and Linux.

What stays closed outside the tunnel at each moment:

  • open: Rosetun closes nothing. While connected in TUN, programs' traffic still goes into the tunnel; nothing stops it from going around if the tunnel fails.
  • DNS closed: system DNS cannot leave outside the tunnel; everything else is open.
  • closed: nothing leaves outside the tunnel. In the proxy mode, nothing but the engine and loopback.
  • held: closed, and it stays closed until you connect or run rosetun open-network.
  • * read from the code: no matrix scenario covers this cell. Every other cell has a scenario in tools/vm; a release's notes say which matrices were run for it.

"No protection" means the kill switch is off and the DNS lock is not in place: the firewall refused it, or the tunnel has no DNS of its own. On Windows sing-box closes port 53 outside the tunnel by itself while it runs, so system DNS can leave only while it restarts, or after the service stops. On Linux a program that picks the physical interface itself can also send DNS past the tunnel while connected.

Windows

EventNo protectionDNS lockKill switchLockdownProxyProxy, kill switch
Disconnectedopenopenopenclosedopenopen*
ConnectedopenDNS closedclosedclosedopenclosed
Engine restartopenDNS closedclosedclosed*open*closed
Service crashopen*openopenclosedopen*open*
Service stoppedopen*open*openclosedopen*open*
Updateopen*openheldclosedopen*held*
Restart of the computeropen*open*open*closedopen*open*

Linux

EventNo protectionDNS lockKill switchLockdownProxyProxy, kill switch
Disconnectedopenopenopenclosedopenopen
ConnectedopenDNS closedclosedclosedopenclosed
Engine restartopenDNS closed*closedclosed*open*closed
Service crashopen*DNS closed until the service restarts, then openheldclosedopen*held*
Service stoppedopen*open*openclosedopen*open
Updateopen*DNS closed until the new service starts, then open*heldclosedopen*held*
Restart of the computeropen*open*open*closedopen*open*

The difference to remember: on Windows a crash of the service opens the network, because the firewall removes a session's filters with its process, and only Lockdown stays. On Linux the firewall table outlives the service, so a kill switch holds the network closed after a crash. A restart of the computer opens both, except under Lockdown. On Windows a hold from an update is Lockdown's persistent set, so by the code it also lasts through a restart (no scenario covers it); on Linux it does not.

Not tested:

  • Windows 10 in the failure tests: it is only known to run on one tester's computer;
  • other firewalls and antivirus programs with their own network filters, and firewalld on Linux (Rosetun's units start after it; nftables.service is covered);
  • sleep and hibernation with Lockdown on real hardware (Windows: only a virtual machine's sleep; Linux: not at all);
  • a power cut on Linux;
  • going back to 0.4;
  • on Linux, Local network from a program that does not pick the interface itself;
  • on Linux, the window, the tray and the polkit prompt in an automated run: no matrix drives a desktop. GNOME was checked by hand; KDE Plasma was not, on Wayland or X11.

Lockdown protects against accidental leaks: the VPN drops, the service stops, the computer boots. It does not protect against malware you run yourself. The kill switch stays the main protection.