My VPN provider is listed as "vulnerable" but testing with their test site does not show IP leak...
Which one?
VPN leaks users’ IPs via WebRTC
71–80 of 172 posts
Re: VPN leaks users’ IPs via WebRTC
#72Given that its hard to figure out how they could be profitable, should we assume private internet access is a NSA honeypot?
Seems very unlikely to me. Both the founder (Andrew Lee) and the CEO (Ted Kim) are known in the industry, have made their views on encryption and authoritarianism pretty clear in interviews, articles, and even full-page ads in the NYT and WaPo to argue for broadband privacy[0] and encryption. PIA also seems pretty profitable; they certainly have enough to contribute to various open source projects, join pro-net-neutr…
What's your take on the recent releases that claim that the US government is funding the Tor network and its development? Information obtained from FOIA requests.
Re: VPN leaks users’ IPs via WebRTC
#73Just want to point anyone looking to test their own VPN to https://ipleak.net/ . That's been my go-to, and it seems more comprehensive than the linked service.
FWIW, I show that Opera's free VPN does not leak the client's IP address. https://www.opera.com/computer/features/free-vpn
Operas VPN is not even a VPN tho. Check their phrasing they call it 'Web vpn' or something like this and already committed in the past that the naming scheme for their proxy was just a marketing trick.
Written from Opera tho. So not saying it sucks :)
Re: VPN leaks users’ IPs via WebRTC
#74This is a terminology problem. If you are using a VPN, a browser could not possibly leak your real IP, as all traffic would be encapsulated by the VPN.
What is being described is actually a proxy.
Re: VPN leaks users’ IPs via WebRTC
#75Clickbait? Its not "VPN providers" its "VPN provider software", I never even thought of using their software, most just give you the credentials for OpenVPN/IPSEC/PPTP or similar. Also if anonymity is of "real" concern you should never use a system that knows your real IP address in the first place. Instead create the vpn tunnel on a separate host system and run something like Tails in a VM (or better yet separate ph…
>Its not "VPN providers" its "VPN provider software" OpenVPN leaks DNS on every default Ubuntu installation I have tried. But I think it's actually Ubuntu NetworkManager's fault. The WebRTC leaks discussed in this article are not prevented by OpenVPN either (last time I checked, which was a while ago). You have to disable WebRTC in the browser.
use sshuttle -dns $server
Re: VPN leaks users’ IPs via WebRTC
#76Earlier quoted context omitted.
>Its not "VPN providers" its "VPN provider software" OpenVPN leaks DNS on every default Ubuntu installation I have tried. But I think it's actually Ubuntu NetworkManager's fault. The WebRTC leaks discussed in this article are not prevented by OpenVPN either (last time I checked, which was a while ago). You have to disable WebRTC in the browser.
>You have to disable WebRTC in the browser Incorrect. An easy and foolproof way of using VPNs is with network namespaces. You start the VPN in your init network namespace and then move the created device into a dedicated VPN namespace. OpenVPN has support for this because it allows you to execute a shell script after the VPN device has been created. Then you simply start your browser, torrent client, whatever in this…
>DNS leaks can be prevented by using a generic DNS provider such as 8.8.8.8
You mean leaking to Google doesn't count as leaking?
Your namespaces suggestion is interesting, but easy and foolproof?
Re: VPN leaks users’ IPs via WebRTC
#77Just want to point anyone looking to test their own VPN to https://ipleak.net/ . That's been my go-to, and it seems more comprehensive than the linked service.
[deleted]
Re: VPN leaks users’ IPs via WebRTC
#78Earlier quoted context omitted.
Seems very unlikely to me. Both the founder (Andrew Lee) and the CEO (Ted Kim) are known in the industry, have made their views on encryption and authoritarianism pretty clear in interviews, articles, and even full-page ads in the NYT and WaPo to argue for broadband privacy[0] and encryption. PIA also seems pretty profitable; they certainly have enough to contribute to various open source projects, join pro-net-neutr…
What's your take on the recent releases that claim that the US government is funding the Tor network and its development? Information obtained from FOIA requests.
They created Tor, and have been funding it from the start. This is not news.
Yasha Levine has been on a tear ‘exposing’ this for the last few years, but it’s not personally shocking to me.
Did you know that the US government funded Signal, too?
Re: VPN leaks users’ IPs via WebRTC
#79Earlier quoted context omitted.
I can appreciate the use of Tails in a VM, but doesn't the provider of the "separate host system" have your identity through your payment information?
Running Tails in a VM is so your browser can't leak your real IP to the wider internet even if it wants to, because it doesn't know what it is. Your VM provider still knows your real IP address.
This is essentially the philosophy behind Whonix.
Re: VPN leaks users’ IPs via WebRTC
#80I don't use VPNs. For me, the more alarming information here is that SOCKS and Tor proxies are also leaking IP addresses. If a SOCKS proxy is configured in browser, isn't it the browser's responsibility to ensure all outgoing traffic - including WebRTC - goes via the proxy? Are these browser bugs? Update: Can confirm Firefox Quantum with SOCKS proxy leaks the address. Oh dear! Update 2: I didn't realize this is how W…
This is the fault of the browser and WebRTC. They know about this but deliberately break it. The truth is WebRTC should never activate without user permission. But no, WebRTC added data-channels. They have no good use to be silent and especially not to override SOCKS proxy. In fact, some key people on the WebRTC group, when I pressed them, could not provide a single real use-case for silent data channels. Firefox is…
It really seems like adding a permission handler with a warning on WebRTC would be an easy fix for this problem and/or browsers should respect proxies and such when generating WebRTC candidates.
And I say that as someone who thinks WebRTC has some pretty cool use cases.