3 ms·

After enabling it I keep seeing my public address here. https://diafygi.github.io/webrtc-ips/ https://diafygi.github.io/webrtc-ips/ — What gives?

by mahouse 11y ago

funkyy 11y ago
But it wont be able to see your IP once hidden behind VPN or Proxie server.
- mahouse 11y ago
  That's bad. I expect to see there only an IP address obtained by using WebRTC, not a detection by using all methods that are possible.
satori99 11y ago
That is odd... for me (Firefox on Windows), enabling that option completely removes the `RTCPeerConnection` property from the global object, and any script that tries to use it fails with `TypeError: RTCPeerConnection is not a constructor`.
sergers 11y ago
i was having the same issue. enabling the option in ublock origin, my local IP would not show but my "Public" IP address still showed. decided to checkout what options are in chrome://flags for webrtc (use to be enable/disable for webrtc but now thats restricted to just android). found this other option in the flags, chrome://flags/#enable-webrtc-stun-origin Enable support for WebRTC Stun origin header. Mac, Windows, Linux, Chrome OS, Android When enabled, Stun messages generated by WebRTC will contain the Origin header. i enabled it, my public IP no longer shows on that site. doesnt matter if i disable/enable ublock, my public IP never shows on that site with that chrome flag enabled. any idea what that flag actually does? and repercussions leaving it enabled?
pmontra 11y ago
I went there with Firefox without ublock and saw my public and local addresses (docker0, eth0 and virbr0 - VirtualBox). I installed Disable WebRTC https://addons.mozilla.org/en-US/firefox/addon/happy-bonobo-disable-webrtc/ https://addons.mozilla.org/en-US/firefox/addon/happy-bonobo-... and all the addresses disappeared. NoScript mitigates the problem because WebRTC won't work with scripts blocked but I'll still have to disable the plugin to make it work on legitimate sites. It's annoying and I'd prefer a browser permission popup along the lines of what has been suggested in other posts here.
- byuu 11y ago
  Going to about:config and setting media.peerconnection.enabled to false seems to work, without the need for an extension. Now to find out how many sites break in fun and exciting ways for having done this ;)
gorhill 11y ago
The real issue is WebRTC exposing your ISP address when behind a VPN. If you are not behind a VPN, it is expected that your ISP address is visible -- WebRTC or not.

After enabling it I keep seeing my public address here. https://diafygi.github.io/webrtc-ips/ https://diafygi.github.io/webrtc-ips/ — What gives?

by mahouse 11y ago

After enabling it I keep seeing my public address here. https://diafygi.github.io/webrtc-ips/ https://diafygi.github.io/webrtc-ips/ — What gives?

funkyy 11y ago

But it wont be able to see your IP once hidden behind VPN or Proxie server.

mahouse 11y ago
That's bad. I expect to see there only an IP address obtained by using WebRTC, not a detection by using all methods that are possible.

satori99 11y ago

That is odd... for me (Firefox on Windows), enabling that option completely removes the `RTCPeerConnection` property from the global object, and any script that tries to use it fails with `TypeError: RTCPeerConnection is not a constructor`.

sergers 11y ago

i was having the same issue. enabling the option in ublock origin, my local IP would not show but my "Public" IP address still showed. decided to checkout what options are in chrome://flags for webrtc (use to be enable/disable for webrtc but now thats restricted to just android). found this other option in the flags, chrome://flags/#enable-webrtc-stun-origin Enable support for WebRTC Stun origin header. Mac, Windows, Linux, Chrome OS, Android When enabled, Stun messages generated by WebRTC will contain the Origin header. i enabled it, my public IP no longer shows on that site. doesnt matter if i disable/enable ublock, my public IP never shows on that site with that chrome flag enabled. any idea what that flag actually does? and repercussions leaving it enabled?

pmontra 11y ago

I went there with Firefox without ublock and saw my public and local addresses (docker0, eth0 and virbr0 - VirtualBox). I installed Disable WebRTC https://addons.mozilla.org/en-US/firefox/addon/happy-bonobo-disable-webrtc/ https://addons.mozilla.org/en-US/firefox/addon/happy-bonobo-... and all the addresses disappeared. NoScript mitigates the problem because WebRTC won't work with scripts blocked but I'll still have to disable the plugin to make it work on legitimate sites. It's annoying and I'd prefer a browser permission popup along the lines of what has been suggested in other posts here.

byuu 11y ago
Going to about:config and setting media.peerconnection.enabled to false seems to work, without the need for an extension. Now to find out how many sites break in fun and exciting ways for having done this ;)

gorhill 11y ago

The real issue is WebRTC exposing your ISP address when behind a VPN. If you are not behind a VPN, it is expected that your ISP address is visible -- WebRTC or not.