Mozilla will soon be landing a series of capabilities to allow users to control many aspects of how ICE candidates are gathered and used.
These include, but aren't limited to, methods to restrict the use of interfaces to either the default route or a whitelisted interface; ability to force use of relay candidates only; to override application specification of ICE servers with a user-specified value (i.e. force use of a border TURN server); and methods to allow extensions to validate if a user has intended to allow use of a PeerConnection. We also are looking into methods to expose 'background' PeerConnections short of blocking all of them or requiring explicit opt-in ahead of time, and how to record what uses PeerConnections, and for what. The meta/tracking bug is *Bug 1189167* <https://bugzilla.mozilla.org/show_bug.cgi?id=1189167>. We expect many of these new tools to be available soon in Firefox Beta 41 (shortly after 40 goes to release in a few weeks). Most of these capabilities will be available initially as interfaces that extensions can enable or users can flip on via about:config. -- Maire Reavy [email protected] _______________________________________________ dev-media mailing list [email protected] https://lists.mozilla.org/listinfo/dev-media
