Opened 3 years ago

Last modified 5 months ago

#20392 needs_information defect

Checking version before authentication

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

Description

Outdated Tor Browser never shows that update is available right from the start. The reason seems to be

[10-09 00:55:01] Torbutton INFO: Checking version with socks port: 9150
getFirstPartyURI failed for https://www.torproject.org/projects/torbrowser/RecommendedTBBVersions: 0x80070057
[10-09 00:55:01] Torbutton INFO: Component returned failure code: 0x80070057 (NS_ERROR_ILLEGAL_VALUE) [mozIThirdPartyUtil.getFirstPartyURIFromChannel]
[10-09 00:55:01] Torbutton INFO: tor SOCKS isolation catchall: https://www.torproject.org/projects/torbrowser/RecommendedTBBVersions via --unknown--:fdd14a957ee8937730d4a7a4753abcba
getFirstPartyURI failed for https://www.torproject.org/projects/torbrowser/RecommendedTBBVersions: 0x80070057
[10-09 00:55:01] Torbutton INFO: controlPort << authenticate 1b2b1735476424387048537a68675d7b
setevents stream
Tor NOTICE: New control connection opened from 127.0.0.1. 
[10-09 00:55:01] Torbutton INFO: controlPort >> 250 OK
[10-09 00:55:01] Torbutton DBUG: Tor socks listener: 127.0.0.1:9150
[10-09 00:55:01] Torbutton INFO: called init()

Child Tickets

Change History (6)

comment:1 Changed 3 years ago by mcs

Cc: brade mcs gk added
Status: newneeds_information

The authenticate log message is generated due to the circuit display code and should not affect the update check.

At least on OSX, I cannot reproduce this problem. Both the update service check and the RecommendedTBBVersions check (used to decide whether to display the "out of date" message on about:tor) occur the first time. What version of Tor Browser are you testing with, and on which OS?

A side note: I noticed that https://www.torproject.org/projects/torbrowser/RecommendedTBBVersions still contains 6.5a2, which may be an error.

comment:2 in reply to:  1 Changed 3 years ago by cypherpunks

Replying to mcs:

A side note: I noticed that https://www.torproject.org/projects/torbrowser/RecommendedTBBVersions still contains 6.5a2, which may be an error.

Now it is:

[
"6.0.5",
"6.0.5-Linux",
"6.0.5-MacOS",
"6.0.5-Windows",
"6.0.6",
"6.0.6-Linux",
"6.0.6-MacOS",
"6.0.6-Windows",
"6.5a3",
"6.5a3-Linux",
"6.5a3-MacOS",
"6.5a3-Windows",
"6.5a3-hardened",
"6.5a3-hardened-Linux",
"6.5a4",
"6.5a4-Linux",
"6.5a4-MacOS",
"6.5a4-Windows",
"6.5a4-hardened",
"6.5a4-hardened-Linux"
]

comment:3 Changed 2 years ago by cypherpunks

And now:

[
"6.5",
"6.5-Linux",
"6.5-MacOS",
"6.5-Windows",
"6.5.1",
"6.5.1-Linux",
"6.5.1-MacOS",
"6.5.1-Windows",
"7.0a1",
"7.0a1-Linux",
"7.0a1-MacOS",
"7.0a1-Windows",
"7.0a1-hardened",
"7.0a1-hardened-Linux",
"7.0a2",
"7.0a2-Linux",
"7.0a2-MacOS",
"7.0a2-Windows",
"7.0a2-hardened",
"7.0a2-hardened-Linux"
]

(What about using SOS?)

comment:4 in reply to:  3 Changed 2 years ago by gk

Replying to cypherpunks:

And now:

[
"6.5",
"6.5-Linux",
"6.5-MacOS",
"6.5-Windows",
"6.5.1",
"6.5.1-Linux",
"6.5.1-MacOS",
"6.5.1-Windows",
"7.0a1",
"7.0a1-Linux",
"7.0a1-MacOS",
"7.0a1-Windows",
"7.0a1-hardened",
"7.0a1-hardened-Linux",
"7.0a2",
"7.0a2-Linux",
"7.0a2-MacOS",
"7.0a2-Windows",
"7.0a2-hardened",
"7.0a2-hardened-Linux"
]

(What about using SOS?)

That's #21718.

comment:5 Changed 6 months ago by gk

Keywords: tbb-updater added

comment:6 Changed 5 months ago by gk

Keywords: tbb-update added; tbb-updater removed

Renaming keyword to make it a bit broader

Note: See TracTickets for help on using tickets.