Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • T Tor Browser
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1,284
    • Issues 1,284
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 7
    • Merge requests 7
  • Deployments
    • Deployments
    • Releases
  • 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 Browser
  • Issues
  • #40042

Closed
Open
Created Jul 27, 2020 by Mark Smith@mcs

decide if we need a watershed update prior to our esr78-based Tor Browser

Firefox 72.0.2 was a watershed release: all users of older versions are first updated to 72.0.2 before getting an update to the current release. Why? Because Mozilla removed the code that knew how to migrate from key3.db to key4.db. Should we force all Tor Browser users to update to our last esr68-based Tor Browser so they have key4.db the first time they run an esr78-based Tor Browser? I am not 100% sure, but I think key3.db was only used for storing passwords (and maybe only the master NSS password?)

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