Opened 4 years ago

Closed 4 years ago

#14152 closed defect (fixed)

"Expert Bundle" download button is linked to an outdated version of Tor

Reported by: cypherpunks Owned by: gk
Priority: High Milestone:
Component: Webpages/Website Version: Tor: 0.2.5.10
Severity: Keywords: TorBrowserTeam201502, MikePerry201502R
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

The current stable version of Tor is 0.2.5.10, but in the "Microsoft Windows" section of the "Download Tor" page at URL https://www.torproject.org/download/download.html.en, the "Expert Bundle" download button is linked to https://www.torproject.org/dist/win32/tor-0.2.4.23-win32.exe.

However in the folder https://dist.torproject.org/torbrowser/4.0.2/ there is a file named "tor-win32-tor-0.2.5.10.zip" (and the associated "tor-win32-tor-0.2.5.10.asc") that allegedly contains the current version of Tor for MS Windows.

Child Tickets

Attachments (1)

0001-Bug-14152-Update-expert-bundle-tor-version.patch (879 bytes) - added by gk 4 years ago.

Download all attachments as: .zip

Change History (13)

comment:1 Changed 4 years ago by cypherpunks

Priority: normalmajor

comment:2 Changed 4 years ago by Sebastian

Resolution: fixed
Status: newclosed

Fixed I hope

comment:3 Changed 4 years ago by cypherpunks

Resolution: fixed
Status: closedreopened

Thanks for your effort, but now the link "Download Expert Bundle" -> https://www.torproject.org/dist/win32/tor-0.2.5.10-win32.exe is broken because it points to a non existent "tor-0.2.5.10-win32.exe" file in the /win32/ folder.

In fact that folder contains only the following files: tor-0.2.4.22-win32-1.exe, tor-0.2.4.22-win32.exe, tor-0.2.4.23-win32.exe and the related detached signatures.

It seems that new versions of Tor build for MS Windows (not yet in an executable .exe installer, but in a WinZip compressed file), currently tor-win32-tor-0.2.5.10.zip and tor-win32-0.2.6.2-alpha.zip, are stored in the /torbrowser/4.0.x/ (now /torbrowser/4.0.3/) and /torbrowser/4.5*/ (now /torbrowser/4.5a3/) folders, respectively.

comment:4 Changed 4 years ago by Sebastian

Owner: changed from Sebastian to gk
Status: reopenedassigned

I spoke to gk about this, it seems the way the expert bundle is currently built doesn't allow a stable location/update along with the rest. I'll defer to him on whether we should take down the link for now or what.

comment:5 Changed 4 years ago by arma

Sebastian: the challenge here is that our website wml macros don't know how to update to the new tor browser directory, so every time tor browser's version changes, this windows zip url goes 404.

More wml hacking will be helpful here I think.

comment:6 Changed 4 years ago by arma

Ok, I just changed the links to accurately point inside the dist/torbrowser/<version-torbrowserbundledir>/ directory.

It is still the case that somebody will need to change the <version-win32-stable> tag whenever Tor Browser switches Tor versions. :(

We could make it a little bit better by just using <version-stable> directly, so it updates whenever a new Tor tarball comes out, and is 404 for the time period between that tarball and when Tor Browser puts out an update. That's more automated but still not ideal.

Also, it would seem that package-win32-alpha is unused. Maybe we should take this opportunity to drop it?

comment:7 in reply to:  6 ; Changed 4 years ago by gk

Replying to arma:

Ok, I just changed the links to accurately point inside the dist/torbrowser/<version-torbrowserbundledir>/ directory.

It is still the case that somebody will need to change the <version-win32-stable> tag whenever Tor Browser switches Tor versions. :(

We could put that requirement into our ReleaseProcess document. Should not be too much overhead as we need to change Tor Browser related versions anyway every time we do a new release.

We could make it a little bit better by just using <version-stable> directly, so it updates whenever a new Tor tarball comes out, and is 404 for the time period between that tarball and when Tor Browser puts out an update. That's more automated but still not ideal.

I think I'd prefer the above idea. Otherwise this would leave a 6 week gap (worst case) which is probably pretty confusing to users.

Also, it would seem that package-win32-alpha is unused. Maybe we should take this opportunity to drop it?

Dunno. Pointing version-win32-alpha to "0.2.6.2-alpha" would at least give a functional expert bundle with an alpha tor. I am wondering if the "Expert Bundle" by definition should include the latest alpha version instead of a stable one.

comment:8 in reply to:  7 Changed 4 years ago by cypherpunks

Replying to gk:

Dunno. Pointing version-win32-alpha to "0.2.6.2-alpha" would at least give a functional expert bundle with an alpha tor. I am wondering if the "Expert Bundle" by definition should include the latest alpha version instead of a stable one.

We can link both stable and alpha in the Expert Bundle section of the Download Tor page as for the Tor Browser.

comment:9 in reply to:  7 Changed 4 years ago by arma

Replying to gk:

It is still the case that somebody will need to change the <version-win32-stable> tag whenever Tor Browser switches Tor versions. :(

We could put that requirement into our ReleaseProcess document. Should not be too much overhead as we need to change Tor Browser related versions anyway every time we do a new release.

Yes please!

comment:10 Changed 4 years ago by gk

Keywords: TorBrowserTeam201502 TorBrowserTeam201502R MikePerry201502R added
Status: assignedneeds_review

I added a patch to the ReleaseProcess documentation. For now we stick with putting the stable version into the expert bundle. Having the alpha version in it or having an expert and an expert expert bundle (the former with stable tor and the latter with alpha tor) is a different ticket.

comment:11 Changed 4 years ago by mikeperry

Keywords: TorBrowserTeam201503R added; TorBrowserTeam201502R removed

comment:12 Changed 4 years ago by mikeperry

Keywords: TorBrowserTeam201503R removed
Resolution: fixed
Status: needs_reviewclosed

Applied this patch. Thanks!

Note: See TracTickets for help on using tickets.