[tor-bugs] #6847 [Tor Check]: tor-browser-gnu-linux-x86_64-2.2.39-1-dev-en-US and check don't agree on latest version
Tor Bug Tracker & Wiki
torproject-admin at torproject.org
Fri Sep 14 20:34:35 UTC 2012
#6847: tor-browser-gnu-linux-x86_64-2.2.39-1-dev-en-US and check don't agree on
latest version
-----------------------+----------------------------------------------------
Reporter: phobos | Owner:
Type: defect | Status: new
Priority: normal | Milestone:
Component: Tor Check | Version:
Keywords: | Parent:
Points: | Actualpoints:
-----------------------+----------------------------------------------------
Comment(by rdump):
I see this sometimes/most times today (2012-09-14) on TorBrowser-2.2.39-1
-osx-x86_64-en-US on two Mac OS X 10.6.8 systems. It appears to happen
after the first launch of a new install of TorBrowser-2.2.39-1-osx-x86_64
-en-US for me.
At the first launch on each system, check.torproject.org did not indicate
a security update was available (~15:00 and ~17:00 UTC).
I configured each TBB to test a new private bridge (running 0.2.3.22-rc on
OpenBSD 5.1), and relaunched the TBB. Through the bridge, I was then
informed by check.torproject.org "There is a security update available for
the Tor Browser Bundle" (~15:00 and ~17:00 UTC). Reconfiguring to not use
the bridge and relaunching on one of the test systems resulted in "There
is a security update available for the Tor Browser Bundle" (~22:10 &
~22:20 UTC).
Replacing the TorBrowser-2.2.39-1-osx-x86_64-en-US TorBrowser_en-US.app
with a fresh copy resulted in check.torproject.org not telling me a
security update is available (~22:25 UTC). Quitting and restarting that
copy (no config changes beyond window positions) returned me to "There is
a security update available for the Tor Browser Bundle" (~22:30 UTC).
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/6847#comment:3>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
More information about the tor-bugs
mailing list