PrivSec-dev/privsec.dev
1
0
Fork 0
mirror of https://github.com/PrivSec-dev/privsec.dev synced 2025-02-20 18:31:35 -05:00
Code

Grammar

Browse Source 
Signed-off-by: Tommy <contact@tommytran.io>
This commit is contained in:
Tommy 2022-10-08 05:57:06 -04:00
parent 8dad84452a
commit 1d2427b36f
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
content/apps/ProtonVPN IP Leakage on Linux and Workaround.md
View File

@ -13,8 +13,8 @@ I sent Proton an email regarding this issue in late August 2022 and was told the
Ideally, when implementing a killswitch, a VPN client should drop all connections on non-VPN interfaces except when the connection is to the VPN provider's servers. This is necessary to prevent accidental leaks, at least by unprivileged applications. Unfortunately, the ProtonVPN client does not currently do this.
Effectively, any application that binds to the public interface on your Linux system will expose your actual IP address when they connect to the internet regardless of whether you have the killswitch on, off, or "permanently" (persistently) enabled. This is problematic, especially for certain applications like Torrent clients, as they tend to use whatever interface they have access to to connect to the internet.
Effectively, any application that binds to the public interface on your Linux system will expose your actual IP address when they connect to the internet regardless of whether you have the killswitch on, off, or "permanently" (persistently) enabled. This is problematic, especially for certain applications like Torrent clients, as they tend to use whatever interfaces they have access to (rather than just the default one) to connect to the internet
.
You can check this with `curl`:
```bash