Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Tor Browser Tor Browser
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 922
    • Issues 922
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 4
    • Merge requests 4
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
    • Model experiments
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Applications
  • Tor BrowserTor Browser
  • Issues
  • #41671

Turn media.peerconnection.ice.relay_only to true as defense in depth against WebRTC ICE leaks

From this note:

The "safer" option [to avoid leaks in a WebRTC-enabled scenario] would be dis-allow the usage of the so called host candidates. In the most privacy conserving scenario only use TURN candidates. TURN servers are relays which are meant to help traverse restrictive NATs, but since they are relaying they also effectively hide the publicly routable IP address of your ISP/uplink. Firefox has an about:config parameter called "media.peerconnection.ice.relay_only", which makes Firefox WebRTC stack only connect via TURN.

Edited Mar 09, 2023 by ma1
Assignee
Assign to
Time tracking