Opened 3 years ago

Closed 3 years ago

#15637 closed defect (fixed)

Update loop due to mismatched Tor Browser version

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

Description

Due to a Tor security update, we tried to quicken the TBB release by only rebuilding Tor, since the browser did not change.

Unfortunately, the TBB version is now compiled in to the browser for the updater, and the 4.0.7 TBB thought it was still 4.0.6 for updates. This caused an update loop, where the 4.0.7 TBB kept trying to update to itself.

Child Tickets

Change History (3)

comment:1 Changed 3 years ago by mcs

Cc: brade mcs added

As you have probably figured out by now, the only solution is to rebuild the browser and re-release 4.0.7 (or even better, use 4.0.8 for the new release to avoid confusion).

The reason that the Tor Browser version is not just pulled from the torbrowser.version preference as in the past is because sometimes the Mozilla updater and update service code need the browser version even though prefs. are not available.

comment:2 Changed 3 years ago by boklm

I have updated the test suite to check that the torbrowser.version preference is the same as the version from the filename:
https://gitweb.torproject.org/boklm/tor-browser-bundle-testsuite.git/commit/?id=c46a28ad955881ce60882c680354589eba698575

comment:3 Changed 3 years ago by gk

Resolution: fixed
Status: newclosed

Fixed in 4.0.8.

Note: See TracTickets for help on using tickets.