Opened 3 years ago

Last modified 8 months ago

#18375 new defect

HTTPSEverywhere/NoScript becomes disabled and not shown in about:addons after some launches.

Reported by: cypherpunks Owned by: tbb-team
Priority: Medium Milestone:
Component: Applications/Tor Browser Version:
Severity: Normal Keywords: tbb-security, noscript
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

HTTPSEverywhere becomes disabled and not shown in about:addons after some launches.

Child Tickets

Change History (6)

comment:1 Changed 3 years ago by cypherpunks

In years of heavy usage I have never seen such behaviour in Tor Browser.

Please provide details.

comment:2 Changed 3 years ago by mcs

Status: newneeds_information

comment:3 Changed 10 months ago by cypherpunks

Keywords: tbb-security added
Summary: HTTPSEverywhere becomes disabled and not shown in about:addons after some launches.HTTPSEverywhere/NoScript becomes disabled and not shown in about:addons after some launches.

How it works with TBB 7.5.5 (NoScript 5.1.8.6):

Tor NOTICE: Heartbeat: Tor's uptime is 4 days 6:20 hours, with 0 circuits open. I've sent 22.72 MB and received 100.46 MB. 					
Tor WARN: comparing times on millisecond detail too far apart: 31581236 seconds 					
Tor NOTICE: Your system clock just jumped 31581238 seconds forward; assuming established circuits no longer work. 					
Tor NOTICE: Heartbeat: Tor's uptime is 4 days 8:12 hours, with 0 circuits open. I've sent 22.98 MB and received 101.07 MB. 					
Tor WARN: Received a bad CERTS cell: At least one certificate expired. 					
Tor NOTICE: Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit) 					
addons.update-checker	WARN	Request for https://secure.informaction.com/download/classic/?v=5.1.8.5 timed out		
addons.xpi	WARN	Add-on {73a6fe31-595d-460b-a920-fcc0f8843232} is not correctly signed.		
No matching message handler for the given recipient.  MessageChannel.jsm:621					

i.e. with clock skew (1y forward), auto update of add-ons disables NoScript.
After setting the time correctly, NoScript is still disabled and:

addons.update-checker	WARN	onUpdateCheckComplete failed to parse update manifest: [Exception... "Update manifest is missing a required addons property."  nsresult: "0x80004005 (NS_ERROR_FAILURE)"  location: "JS frame :: resource://gre/modules/addons/AddonUpdateChecker.jsm :: getRequiredProperty :: line 473"  data: no] Stack trace: getRequiredProperty()@resource://gre/modules/addons/AddonUpdateChecker.jsm:473 < parseJSONManifest()@resource://gre/modules/addons/AddonUpdateChecker.jsm:483 < UpdateParser.prototype.onLoad/parser()@resource://gre/modules/addons/AddonUpdateChecker.jsm:655 < UpdateParser.prototype.onLoad()@resource://gre/modules/addons/AddonUpdateChecker.jsm:675 < UpdateParser/<()@resource://gre/modules/addons/AddonUpdateChecker.jsm:593 < onStopRequest()@resource://gre/modules/WebRequest.jsm:347			
addons.xpi	WARN	Add-on {73a6fe31-595d-460b-a920-fcc0f8843232} is not correctly signed.			

Only after updating and parsing add-ons blocklist, and then updating add-ons, NoScript is enabled again.

comment:4 Changed 10 months ago by gk

Interesting, I wonder what to do about it, though...

comment:5 Changed 10 months ago by cypherpunks

Status: needs_informationnew

comment:6 Changed 8 months ago by traumschule

Keywords: noscript added
Note: See TracTickets for help on using tickets.