[tor-bugs] #13406 [Tor Browser]: Tor Browser 4.0 should not warn users their version is outdated unless it can't fetch updates
Tor Bug Tracker & Wiki
blackhole at torproject.org
Fri Oct 17 23:06:31 UTC 2014
#13406: Tor Browser 4.0 should not warn users their version is outdated unless it
can't fetch updates
-----------------------------+---------------------------
Reporter: Sherief | Owner: tbb-team
Type: enhancement | Status: new
Priority: normal | Milestone:
Component: Tor Browser | Version:
Resolution: | Keywords: tbb-usability
Actual Points: | Parent ID:
Points: |
-----------------------------+---------------------------
Comment (by Sherief):
Replying to [comment:3 brade]:
> For 4.0, my assumption was that we should keep both update mechanisms in
place (hedging our bets a little on the new updater). I do agree that it
is a little strange to not even mention the built-in updater on about:tor,
but I think it is too late to change strings, etc. for the 4.0 release.
Mike, do you agree?
>
> Also, we need to think about where we are headed in the long run. After
we make the built-in updater more secure (for example, see #13379), then
in my opinion we should not point users to a manual download process at
all.
>
> In the interim period before the built-in updater is checking
signatures, etc. we should probably offer two options (perhaps two
buttons?) on the about:tor page:
> {{{
> [Update to Tor Browser 4.5] [Manually Download Tor
Browser]
> }}}
> What do other people think? Having two buttons seems a little silly and
potentially confusing, but may be necessary for now to satisfy our diverse
community.
What if we can avoid buttons and make a select menu [Update] -> a) Check
for updates b) Manual update within TorButton?
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/13406#comment:6>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
More information about the tor-bugs
mailing list