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
  • #21912
Closed
Open
Created Apr 10, 2017 by Yawning Angel@yawning

Deal with the deprecation of the `hardened` channel.

Per: https://trac.torproject.org/projects/tor/ticket/20814#comment:11

The hardened channel for Tor Browser is going away. The sandbox will need updates for this.

Easy changes:

  • Make it impossible to install the hardened channel.
  • The selfrando specific "disable AESNI in NSS" workaround should apply to the alpha channel.

Release after the hardened removal:

  • Remove ASAN specific workarounds.
  • Purge the remnants of hardened except for the migration path (Can/should be done immediately if the migration path for sandboxed users is a reinstall).

How the actual migration from hardened to alpha is handled on the sandboxing end is currently an open question. The easy thing to do would be to force a reinstall, but people probably don't realize that a reinstall will obliterate all existing preferences and bookmarks. The more involved fix would be to modify the updater to handle channel migration.

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