adrelanos/vpn-firewall

fix shared VPN/Tor server leak bug

adrelanos opened this issue · 1 comments

adrelanos commented

problem description:

If a Tor entry guard is running on the same server (same IP) as the VPN server (same IP), and if VPN breaks down, Tor may connect directly to the VPN if it happened to choose that Tor relay (same IP) as entry guard. This is not that unlikely, because a lot VPN providers support VPN port forwarding, use public IPs and people host Tor servers behind VPN's.

(partial solution):

(A partial solution for this to set the VPN VM's firewall rules to allow connections only to the VPN server. Specifying destination port in that firewall rule should help a lot. Some cases will not be solved (like VPN running on 443).)

full solution:

A full solution is to allow only user tunnel to connect to the open internet. All other users not.

TODO:

  • Implement the full solution.
  • Build on top of the development branch.

starting point:

This was fixed in a similar firewall project. This was fixed in whonix-ws-firewall and whonix-gw-firewall. (These are firewalls tailored for Whonix that will not work as drop in replacement for vpn-firewall.)

tickets:

git commits:

documentation and implementation notes [as footnotes]:

The usability-misc package simplifies this by requesting less file creation from the user. [1] [2]

Footnotes:

[1] The user needs to comment in a few things to make it work. Here in vpn-firewall we could emulate/duplicate these configuration files and have them commented in by default.
[2] Can conflict with whonix-(gw|ws)-firewall but not with usability-misc. [3]
[3] Not have same file names as in usability-misc package so these can still be co-installed.

Bounty too low?:

  1. Go to https://www.bountysource.com/issues/33959514-shared-vpn-tor-server-leak-bug
  2. Click on "Developers"
  3. Click on "Get Started"
  4. Select Status "Bounty too low"
  5. Enter your offer and press "Save".
adrelanos commented

This is done in development branch.