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

Consider enabling WebRTC in the future #86

Open
pyllyukko opened this issue Nov 24, 2015 · 6 comments
Open

Consider enabling WebRTC in the future #86

pyllyukko opened this issue Nov 24, 2015 · 6 comments

Comments

@pyllyukko
Copy link
Owner

See #84.

@nodiscc
Copy link
Contributor

nodiscc commented Mar 20, 2017

Firefox 52 is the new ESR - in which the LAN IP address leak is fixed. So we should either:

  • comment out the pref disabling WebRTC (media.peerconnection.enabled)
  • leave it as is for hardening purposes, and close this issue
  • if notable functionality breakage is found due to WebRTC being disabled, add a NOTICE: field alongside that pref.

@fmarier
Copy link
Contributor

fmarier commented Mar 20, 2017

media.peerconnection.ice.default_address_only should also be removed since the way to disable the leaking of internal IP addresses is media.peerconnection.ice.no_host in Firefox >= 52.

@nodiscc
Copy link
Contributor

nodiscc commented Mar 20, 2017

@fmarier media.peerconnection.ice.no_host is already present (https://github.com/pyllyukko/user.js/blob/master/user.js#L61)

media.peerconnection.ice.default_address_only is there for legacy reasons (with a clear indicator that this is for firefox < 51).

Or should we remove all prefs for versions older than the current ESR? (whole other issue)

@pyllyukko
Copy link
Owner Author

pyllyukko commented Mar 20, 2017

leave it as is for hardening purposes, and close this issue

I would say we keep it disabled for now and revisit this issue a bit later.

if notable functionality breakage is found due to WebRTC being disabled, add a NOTICE: field alongside that pref.

Of course.

@fmarier media.peerconnection.ice.no_host is already present (https://github.com/pyllyukko/user.js/blob/master/user.js#L61)

The comment in user.js says Firefox >= 51 and @fmarier said it's Firefox >= 52...

media.peerconnection.ice.default_address_only is there for legacy reasons (with a clear indicator that this is for firefox < 51).

Yep.

Or should we remove all prefs for versions older than the current ESR? (whole other issue)

No. At least not yet, as ESR 52 is just out of the oven and some distros are still using ESR 45.*.

@nodiscc
Copy link
Contributor

nodiscc commented Mar 21, 2017

No. At least not yet, as ESR 52 is just out of the oven and some distros are still using ESR 45.*.

#251

The comment in user.js says Firefox >= 51 and @fmarier said it's Firefox >= 52...

Yes, this should be clarified. @fmarier is probably right, will edit the comment.

I will amend #249 to re-disable WebRTC. If there are not other points to discuss I think this issue can be closed (changes like this can be tracked in #251)

pyllyukko added a commit that referenced this issue Mar 22, 2017
Re-enable WebRTC, unshorten all links, fixes #86 #244
@nodiscc
Copy link
Contributor

nodiscc commented Apr 16, 2017

WebRTC was re-enabled in 9763829, then re-disabled in ac1a818. This issue should be reopened.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants