Uses Netflix WebRTC

Firefox & Chrome: WebRTC reveals IP even despite using VPN

Anyone who uses a VPN service or a corresponding browser extension does not really want their "original IP" to be recognizable with little effort. A developer has now shown how an unfavorable implementation of WebRTC in Chrome and Firefox can still reveal the IP and thus the location of a user. According to the programmer Daniel Roesler (via TorrentFreak & Caschy), a server operator can determine the IP address of a user despite VPN if the user uses Chrome or Firefox. The background is their support for WebRTC, which is actually intended for communication applications.

Because both browsers are designed so that users with a firewall can also use WebRTC, the approach shown by Roesler can be used to determine the original IP using JavaScript. The website provider only has to deliver a certain piece of code, with the help of which a so-called STUN server spits out the original IP of the VPN user.

Roesler's example shows the whole thing using a publicly accessible server operated by Firefox provider Mozilla itself. For users of VPNs and proxy plugins, this very simple method is likely to be annoying mainly because it offers service providers another option to determine the origin of their requests.

To work around the "problem", VPN users can reconfigure their Firefox browser by changing the setting media.peerconnection.enabledsimply switch to "False" in "About: Config". Chrome users have the option of installing the WebRTC Block extension, which also protects against involuntary disclosure of information via WebRTC. Perhaps you can at least partially prevent US services like Hulu or Netflix from displaying an error despite VPN, because the operators are able to determine the origin of a request despite attempts at obfuscation. Google, IP address, WhoisGoogle / Microsoft / Mozilla / Apple

More on the subject:Chrome

Recommend this message