Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Firefox] Ability to completely disable WebRTC #2853

Closed
gorhill opened this issue Aug 9, 2017 · 6 comments
Closed

[Firefox] Ability to completely disable WebRTC #2853

gorhill opened this issue Aug 9, 2017 · 6 comments
Labels

Comments

@gorhill
Copy link
Owner

gorhill commented Aug 9, 2017

Firefox's WebExtensions API support the complete disabling of WebRTC. Make this option available to user.

The current option "Prevent WebRTC from leaking local IP addresses" will become a sub-option of "Disable WebRTC". For platform not supporting the disabling of WebRTC, the option "Disable WebRTC" will be disabled (dimmed) and always checked.

@gorhill gorhill changed the title [Firefox] Ability to completely disableWebRTC [Firefox] Ability to completely disable WebRTC Aug 9, 2017
@jspenguin2017
Copy link
Contributor

For platform not supporting the disabling of WebRTC, the option "Disable WebRTC" will be disabled (dimmed) and always checked.

I think that is a bit confusing, maybe disabled and always not checked?

@gorhill
Copy link
Owner Author

gorhill commented Aug 9, 2017

That's right my bad, not checked is what I really meant.

@BilBg
Copy link

BilBg commented Aug 9, 2017

Slimjet (Chromium clone - http://www.slimjet.com/ ) have this in Settings:
(I don't know if they changed the source code of Chromium to accomplish this or it is some "hidden setting" in original Chromium they expose)

The screenshot is from Slimjet Browser Portable 10.0.5.0 (based on Chromium 50.0.2661.75)

Slimjet - Enable WebRTC.png

@zero77
Copy link

zero77 commented Aug 13, 2017

Just a suggestion but, is that not something that would fit in better with uMatrix, you could even add an extra column in the add on menu.

@loganmarchione
Copy link

@gorhill, there is an undocumented permission (privacy) needed in manifest.json. Bug is here.

@gorhill
Copy link
Owner Author

gorhill commented Aug 29, 2017

privacy permission is not undocumented, it has been used by uBO since May 2015.

Repository owner locked and limited conversation to collaborators Aug 29, 2017
@gorhill gorhill closed this as completed Nov 19, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

5 participants