Having WebRTC enabled by default is a huge privacy loss for our users.
See    for some background.
As described in the MozillaWiki, there are a few different options
that we can put in our distro default config to limit this issue:
This prevents Firefox from establishing outbound connections from local
addresses. This effectively disables ICE on almost all machines.
This prevents Firefox from even creating the JS objects needed for
WebRTC (it will appear as if the browser does not support ICE / STUN /
WebRTC at all). This appears to break some popular sites, like Airbnb,
per . Probably too drastic.
This prevents local connections from being established, but allows
external ICE servers to function as "proxy" servers. In combination
with media.peerconnection.use_document_iceservers = false (to prevent
the document from providing its own ICE server list, which would allow
the attacker to get the information anyway), and providing a value for
media.peerconnection.default_iceservers (which would require us to find
or create a privacy-respecting ICE proxy and keep it updated), it would
allow safe use of WebRTC.
Note that this is all from quick reading and referencing of the linked
references and the Firefox source code. If anyone else can find better
or more in-depth information, that'd be great.
My personal opinion with the information presented is that we should use
media.peerconnection.ice.no_host = true. That way the objects can still
be created, but it's not possible to establish outbound connections.
- and the demo located at
which shows your IPs.
A. Wilcox (awilfox)
Project Lead, Adélie Linux