Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #16285
Closed (moved) (moved)
Open
Created Jun 03, 2015 by Georg Koppen@gk

Make sure EME is no tracking risk in Tor Browser

The EME architecture got uplifted to Firefox 37 (https://bugzilla.mozilla.org/show_bug.cgi?id=1137045) and is included in ESR 38 as well. We should make sure there are no accompanying tracking/fingerprinting risks. The best plan is probably to disable EME as Mozilla is doing in its ESR 38 release. We may need a custom patch as Mozilla is basically enabling it

#if !defined(MOZ_UPDATE_CHANNEL) || MOZ_UPDATE_CHANNEL != esr

While we may want to take a deeper look at it when we switch to ESR 45 we should make sure that everything related to EME is really disabled if the respective prefs are set to false.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking