[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #20814 [Applications/Tor Browser]: Pick a more accurate name for the "hardened" Tor Browser
#20814: Pick a more accurate name for the "hardened" Tor Browser
--------------------------------------+--------------------------
Reporter: arma | Owner: tbb-team
Type: defect | Status: new
Priority: Medium | Milestone:
Component: Applications/Tor Browser | Version:
Severity: Normal | Resolution:
Keywords: TorBrowserTeam201704 | Actual Points:
Parent ID: | Points:
Reviewer: | Sponsor:
--------------------------------------+--------------------------
Comment (by mcs):
Replying to [comment:14 boklm]:
> Yes, I think we can point to the alpha version in the XML files in the
hardened channel. One thing I am not sure how to do is changing the
channel configuration in the browser (the `app.update.channel` pref). If I
remember correctly, just pointing to an update in an other channel will
not change the channel the user is following (but maybe I'm wrong). Maybe
mcs and brade have an idea how to do that.
As things stand today, the update channel will be preserved. This is
because the mar file generation process generates `add-if-not`
instructions for the `channel-prefs.js` file, which is where the
`app.update.channel` pref value comes from (and add-if-not will prevent
the updater from overwritin an existing file). We should find out how
Mozilla transitioned the WinXP users from the release channel to esr in
the Firefox 52 timeframe and so something similar if possible.
> If we can't change that easily adding a redirect from the hardened
channel URLs to the alpha channel is an other option, but it is annoying
to have to keep this redirect for an unlimited time.
Agreed.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/20814#comment:16>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs