#21912: Deal with the deprecation of the `hardened` channel. ----------------------------------------------+------------------------- Reporter: yawning | Owner: yawning Type: defect | Status: new Priority: High | Milestone: Component: Applications/Tor Browser Sandbox | Version: Severity: Normal | Resolution: Keywords: | Actual Points: Parent ID: | Points: Reviewer: | Sponsor: ----------------------------------------------+-------------------------
Comment (by yawning): Replying to [comment:4 boklm]: > Replying to [comment:2 yawning]: > > * It's not immediately obvious to me how to detect that a channel switch has happened from the update metadata (https://wiki.mozilla.org/Software_Update:updates.xml_Format). This also applies to the bundle locale. > > Yes, it is not possible to detect it from the update metadata. You can detect it by looking at the file `Browser/defaults/pref/channel-prefs.js`. The switch will be done with a mar file updating this file and the `Browser/update-settings.ini` file only. On a somewhat tangential note, it would be nice if the architecture, channel, and locale for the currently installed bundle was stored in a consistent location across all releases, in a format that is easy to parse (and no, "Javascript Mozilla prefs" is not easy to parse). > The update modifying the channel preferences files should apply correctly, but assuming the sandbox updater is not looking at those files to know the current channel, nothing else will happen and users will stay on the last hardened version. Ah ok. That may be less bad than "everything breaks". -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/21912#comment:5> Tor Bug Tracker & Wiki <https://trac.torproject.org/> The Tor Project: anonymity online _______________________________________________ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs