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.
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?
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`.