Privacytools.io: Suggestion: WebRTC

[Jasper-Ben]

Since the Website is also directed to users who lack in depth knowledge about the technical details I would suggest adding some more context to the WebRTC section. Otherwise those people following the guide might disable it and wonder why e.g. hangout, jitsi or similar isn't working.

Also followup question: The chrome section mentions that there only is a plugin that is easily circumvented. Is this only the case with this specific plugin or is the same problem present in other (firefox) plugins? So far I've been using https://github.com/ChrisAntaki/disable-webrtc-firefox for webRTC control.

[C-O-M-P-A-R-T-M-E-N-T-A-L-I-Z-A-T-I-O-N]

Is this only the case with this specific plugin or is the same problem present in other (firefox) plugins?

IIRC (tested one year ago) uBlock has that same problem in Firefox.

[ghost]

Can't WebRTC be disabled completely in about:config?

[Jasper-Ben]

@Shifterovich It can. But from time to time I want to use WebRTC (e.g. for my selfhosted jitsi instance) without going through the hassle of enabling it in the about:config. The plugin mentioned above gives the possibility to enable/disable it with one click. So I was wondering if this is a widespread problem affecting multiple plugins.

[ghost]

Ah. Well, we should definitely do some research as the claim about the Chrome extension may not be true anymore.

[Atavic]

Firefox and its forks can block WebTRC into about:config or with addons.
Google Chrome has WebRTC built into the application.

You can test if Chrome is revealing your local and public IP addresses here.

Alternatives:

Ungoogled Chromium modifies Chromium to eliminate these APIs, see:
https://github.com/Eloston/ungoogled-chromium/issues/179

Unofficial Google Chromium builds with No Sync • No WebRTC • No Widevine

[ghost]

uBlock origin also has a setting that disables the IP leak created by WebRTC if that's what you're looking for

[Hillside502]

For "capital portal login checks" read "captive portal login checks"

[blacklight447-ptio]

@thorin-oakenpants we also need to take note of this for the rewritten about:config section.

[Mikaela]

I think this may still be relevant as I don't think the new about:config came yet, assigning @blacklight447-ptio and reopening just in case.