WebRTC leakage

Hi all, It came to my attention that Vivaldi leaks absolutely all that can be leaked via the WebRTC standard. Now, while there might be certain useful cases to have WebRTC enabled (like when using certain video-conference web services), why in the world have I to expose my private IP and hardware unique IDs to the world all the time? Not to mention that WebRTC can leak the real IP even when using VPNs. Please state what is the stance of Vivaldi on this topic and if the company will provide any way to turn WebRTC off and on at will. [b]Note for all Vivaldi users that don't know what I'm talking about[/b] Check this link: https://www.browserleaks.com/webrtc There you can see all your personal unique information this browser is openly sharing with the planet every time you connect to a website. [i][b][color=#ff0000]If you are not scary/upset about this, you definitely should.[/color][/b][/i] Regards.

Actually FF suffers from the same issue until you disable WebRTC. However it differs with Chromium (which I really like) in that unlike it in FF you can completely disable the leakage via about:config or installing an Add-on for easier management of those settings.

I believe it would be nice touch, since Vivaldi is 'a browser for our friends' that it provide an extension to disable WebRTC as well - at least all that can be disable, which isn't every part of WebRTC. You know, friends look after their friends.

Actually there are a couple of extensions in Chrome/Chromium marketplaces that helps mitigate WebRTC issues but they lack of a proper button to make it easier to switch WebRTC state.

Thanks msxx for raising this issue; i've been thinking about raising this issue here for ~a week, but hesitated lest i be accused of belonging to the tinfoil hat brigade. :ohmy:

It was only about a week'ish ago that i discovered this thing called WebRTC wrt its security/privacy implications. At the same time i also discovered the HTML5 Canvas Fingerprinting problem. Both these things utterly shocked me. As a direct result of these two factors, i stopped using V as my default browser [also fueled by my weariness of constantly fighting its ongoing unpleasant habit of abruptly losing my sessions, thumbnails [tabs & SD], & ongoing incomplete incorporation of extensions [eg, cannot access their options by right-clicking their icons, but only from the extension page; with my preferred-default UI scaling of 80%, extension drop-down menus/GUIs are unusable by truncation & overflow (Ghostery, for example)]. Until V has resolved all those issues i shall continue to love & cherish it dearly, but not return it to default-hood.

Until V has developed a bit more as said, Slimjet has become my default; x86 version in Win10 x64 VM, & x64 version in my Linux Mint x64 17.2 KDE main OS. I really miss my V's tiled & [sometimes] stackable tabs, my visual tabs, my [sometimes] wonderful SD, my substantial customisability etc of Dear V, & will rush back to it as soon as viable… but in the meantime Slimjet [which i've been trialing for a few months now] has proven very stable &, compared to all the alternatives except V, feature-rich… two BIG FEATURES being its built-in protection [user-selectable] against both WebRTC & HTML5 Canvas Fingerprinting. According to both tests on https://www.browserleaks.com, Slimjet passes with flying colours. In comparison:
[ol]

Vivaldi fails both, natively, but fully passes for WebRTC if that setting is invoked in the uBlock Origin extension.

Opera Dev fails both, natively, & only half-passes for WebRTC if that setting is invoked in the uBlock Origin extension [at which whilst it then hides my Local IP Address, it still shows my Public IP Address].