#19907: NoScript could not be verified and gets disabled after restart
-----------------------------------------+--------------------------
Reporter: gk | Owner: tbb-team
Type: defect | Status: new
Priority: Very High | Milestone:
Component: Applications/Tor Browser | Version:
Severity: Major | Resolution:
Keywords: tbb-usability, tbb-security | Actual Points:
Parent ID: | Points:
Reviewer: | Sponsor:
-----------------------------------------+--------------------------
Comment (by bugzilla):
As you pay much attention to this issue (dunno why), here are some
thoughts on the topic:
What really should be done is a warning about that some component has
failed to initialize.
As reports about NoScript started to appear more often, last updates of
NoScript could be the reason. The scenario is: user starts TBB and
NoScript prepares to update, say .13 to .14; then TBB finds its new
version and prepares to update; user restarts TBB and Check Add-on for
Compatibility is invoked by NoScript update, but there is no Tor
connection ready to check the signature (plus some bugs with early network
connections might exist), so initialization fails. (The same is for
HTTPSE) Firefox users are not affected, because of existed connection or
no bugs with handling of it.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/19907#comment:5>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online