Suggestion: WebRTC #298

New Issue

2017-07-23T13:40:12Z

Jasper-Ben commented

2017-07-23 13:40:12 +00:00

(Migrated from github.com)

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.

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 commented

2017-07-23 13:49:08 +00:00

(Migrated from github.com)

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.

> 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 commented

2017-07-23 13:49:57 +00:00

(Migrated from github.com)

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

Jasper-Ben commented

2017-07-23 13:55:11 +00:00

(Migrated from github.com)

@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 commented

2017-07-23 14:21:17 +00:00

(Migrated from github.com)

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

👍 1

Atavic commented

2017-07-23 16:32:37 +00:00

(Migrated from github.com)

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

Firefox and its forks can block WebTRC into [about:config](https://privacytoolsio.github.io/privacytools.io/#webrtc) 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](https://diafygi.github.io/webrtc-ips/). Alternatives: Ungoogled Chromium modifies Chromium to eliminate these APIs, see: https://github.com/Eloston/ungoogled-chromium/issues/179 [Unofficial Google Chromium](http://chromium.woolyss.com/) builds with No Sync • No WebRTC • No Widevine

👍 1

ghost commented

2017-07-28 08:47:51 +00:00

(Migrated from github.com)

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

❤️ 2

Hillside502 commented

2018-04-03 20:17:16 +00:00

(Migrated from github.com)

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

blacklight447 commented

2019-09-05 13:18:02 +00:00