Maybe the browser should not have access to your real IP when you are using a VPN? so it's the OS's fault?
VPN leaks users’ IPs via WebRTC
121–130 of 172 posts
Re: VPN leaks users’ IPs via WebRTC
#122Would enabling this uBlock option not be perfectly sufficient at preventing this attack? https://github.com/gorhill/uBlock/wiki/Prevent-WebRTC-from-l...
It should unless this is something new? I'm not sure why this is really news. We've known about this problem with WebRTC for quite some time now.
Re: VPN leaks users’ IPs via WebRTC
#123This has been known for a long long time, but keeps coming up in articles as a new finding.
If it's been known from a long time, then it's really unfortunate that nobody so far has bothered to contribute a fix to FF that changes its webrtc config flags correctly when a network proxy is configured.
uBlock Origin has an option to do it[1].
[1] https://github.com/gorhill/uBlock/wiki/Prevent-WebRTC-from-l...
Re: VPN leaks users’ IPs via WebRTC
#124Earlier quoted context omitted.
A decent emergency medical response service is never profitable. It requires a vast amount of hospitals to ensure that there is one local enough to wherever you get ill or injured and they all have to be staffed by lots of different highly qualified specialists who are in as regular practice as possible. If you were going to require that they be profitable, there simply are not enough rich people for the doctors to w…
Good point. I should have been more clear about "non-obvious" funding sources. If a service isn't profitable, but has a clear funding source (philanthropy, government, etc), that is a little different. But the motive for that funding would need to be clear as well. So yeah, charities can be ok.
I can see where you are coming from, I just think obvious profitability is a poor heuristic for trust, not only due to altruism, but also because some people like showing off, some people are pure hobbyists, some people are trying to make art and many people are just downright weird, though not necessarily in a way that is going to really do much damage.
It isn't always as simple as looking for an obvious motive, though I would agree to always keep an eye out for where the money comes from and if there is a game and if you are a mark. However that should apply whether or not something looks profitable on the surface, otherwise you drop all cynicism the moment someone tells you the right story.
Re: VPN leaks users’ IPs via WebRTC
#125If you use computer/phone-based VPN, try https://www.dnsleaktest.com/ or http://dnsleak.com/
I have VPN on my home router with Tomato firmware. All of my devices pass this flawlessly.
Re: VPN leaks users’ IPs via WebRTC
#126Earlier quoted context omitted.
Or try https://www.doileak.com . (Shameless plug of of a project of mine)
> WebRTC IP Leak: Your local IP: 10.41.41.2 . > Your browser supports WebRTC! Your real IP address is visible to every website you visit. > > Web Real-Time Communication (WebRTC) is enabled by default in Firefox, Opera and Google Chrome, and enables video chat, voice calling and P2P sharing from within your browser. > A neat trick, but it allows any website to instantly see your true IP address. The only way to avoid…
Nope, that's not my "real" IP address
Reminds me a bit of this old story: http://sirkan.iit.bme.hu/~kapolnai/fun/bitchecker.html
Re: VPN leaks users’ IPs via WebRTC
#127Earlier quoted context omitted.
If it's been known from a long time, then it's really unfortunate that nobody so far has bothered to contribute a fix to FF that changes its webrtc config flags correctly when a network proxy is configured.
uBlock Origin has an option to do it[1]. [1] https://github.com/gorhill/uBlock/wiki/Prevent-WebRTC-from-l...
Never used it before but will do so now, Thank you!
Re: VPN leaks users’ IPs via WebRTC
#128Earlier quoted context omitted.
More like this: media.peerconnection.turn.disable = true media.peerconnection.use_document_iceservers = false media.peerconnection.video.enabled = false media.peerconnection.video.vp9_enabled = false media.peerconnection.video.h264_enabled = false media.peerconnection.identity.enabled = false media.peerconnection.identity.timeout = 1
I need to find a way to automate the patching of Firefox's about:config when installing a new OS etc, quite a few telemetry/storage/WebRTC tweaks to date now. There is an extension [1] that'll at least disable the IP address gathering (it doesn't look to disable all of the above settings but may have a similar effect if browser.privacy.network.peerConnectionEnabled disables everything): [1] https://github.com/ChrisAn…
The simplest level would to add what settings you want to Prefs.js file.
http://kb.mozillazine.org/Prefs.js_file
If you want the preferences locked the application level and not be overridden or be unchangeable at profile level. Mainly important if you are managing a lot systems. http://kb.mozillazine.org/Locking_preferences
Re: VPN leaks users’ IPs via WebRTC
#129I 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…
https://www.privacytools.io/#webrtc
Thank you for that site. Looks like I have to become more aware of browser internals.
Re: VPN leaks users’ IPs via WebRTC
#130Earlier quoted context omitted.
More like this: media.peerconnection.turn.disable = true media.peerconnection.use_document_iceservers = false media.peerconnection.video.enabled = false media.peerconnection.video.vp9_enabled = false media.peerconnection.video.h264_enabled = false media.peerconnection.identity.enabled = false media.peerconnection.identity.timeout = 1
I need to find a way to automate the patching of Firefox's about:config when installing a new OS etc, quite a few telemetry/storage/WebRTC tweaks to date now. There is an extension [1] that'll at least disable the IP address gathering (it doesn't look to disable all of the above settings but may have a similar effect if browser.privacy.network.peerConnectionEnabled disables everything): [1] https://github.com/ChrisAn…
Look into vendor.js for patching about:config. I know Arch has one for sure in their package.