Opened 4 years ago

Closed 6 weeks ago

Last modified 6 weeks ago

#11789 closed defect (worksforme)

Update now link in old TBB does not point to latest version

Reported by: runa Owned by: tbb-team
Priority: Medium Milestone:
Component: Applications/Tor Browser Version:
Severity: Normal Keywords:
Cc: mikeperry, brade, mcs Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Following the discussion on https://twitter.com/dcuthbert/status/464068236258967552, it sounds like the "Update now" link in an old version of the Tor Browser Bundle points to an old update instead of the latest version. This link may have been hardcoded to point to the bundle that, at that point in time, was the latest version, but it means that someone who tries to update a six month old OS X bundle will be taken to the download page for 3.6, instead of 3.6.1 (see the twitter.com link for a screenshot).

Child Tickets

Change History (6)

comment:1 Changed 4 years ago by gk

See #11798 which seems actually to be the same issue.

comment:2 Changed 4 years ago by mcs

Cc: mikeperry brade mcs added

I stumbled across this bug and did some investigation. Cc: Mike because he may know more.

It would really help to know what version of TBB the original reporter (dcuthbert) was upgrading from.

It looks like the hard-coded download link inside torbutton.js' torbutton_download_update() function pointed here for a while during TBB 3.x development:
https://archive.torproject.org/tor-package-archive/torbrowser/3.0a4

Then to here:
https://blog.torproject.org/category/tags/tbb-30

Then back to the standard location where it has remained ever since:
https://www.torproject.org/download/download-easy.html

All of the above links work, although it would be bad for someone to upgrade to 3.0a4.

As far as I can tell, the link has never been hard-coded to point to something like:
https://www.torproject.org/dist/torbrowser/3.6/

The screenshot on Twitter actually shows a 404 while trying to access a .dmg file under that last location, which makes me wonder if dcuthbert tried to upgrade while someone was in the midst of updating torproject.org for the 3.6.1 release. If so, it would be nice to know so we can close this ticket or morph it into a release-related bug. The dates match (May 7, 2014).

comment:3 Changed 4 years ago by erinn

Keywords: needs-triage added

comment:4 Changed 7 months ago by teor

Severity: Normal

Set all open tickets without a severity to "Normal"

comment:5 Changed 6 weeks ago by arma

Component: Applications/Tor bundles/installationApplications/Tor Browser
Owner: changed from erinn to tbb-team

I'm throwing into the Tor Browser component, so it gets triaged.

Maybe you want to just close it, or maybe you want to put something in place to detect if it happens in the future.

comment:6 Changed 6 weeks ago by gk

Keywords: needs-triage removed
Resolution: worksforme
Status: newclosed

That's from a very old bundle and we are good here, I think.

Last edited 6 weeks ago by gk (previous) (diff)
Note: See TracTickets for help on using tickets.