[tor-bugs] #26520 [Applications/Tor Browser]: NoScript is broken with TOR_SKIP_LAUNCH=1 in ESR 60-based Tor Browser
Tor Bug Tracker & Wiki
blackhole at torproject.org
Tue Aug 28 07:02:36 UTC 2018
#26520: NoScript is broken with TOR_SKIP_LAUNCH=1 in ESR 60-based Tor Browser
-------------------------------------------------+-------------------------
Reporter: gk | Owner:
| pospeselr
Type: defect | Status: new
Priority: High | Milestone:
Component: Applications/Tor Browser | Version:
Severity: Normal | Resolution:
Keywords: ff60-esr, TorBrowserTeam201808, | Actual Points:
noscript |
Parent ID: | Points:
Reviewer: | Sponsor:
-------------------------------------------------+-------------------------
Comment (by arthuredelstein):
Many thanks to rustybird, Giorgio and intrigeri for your work on this!
Replying to [comment:26 rustybird]:
> in the unlikely case that the NoScript WebExtension finishes startup
sooner than the unbootstrapped XPCOM Torbutton extension
Do we know for sure that NoScript loading first is unlikely? I'm not
actually sure about what determines the order of XPIs loading.
If we wanted to be absolutely sure, NoScript could be patched to listen
for a "ping" and reply with a "pong". And then torbutton could repeatedly
send "ping" (say, once a second) until it receives a "pong", and then
proceed by sending the first updateSettings message.
Giorgio, would that sort of patch sound reasonable to you? If so, I can
send a pull request.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/26520#comment:33>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
More information about the tor-bugs
mailing list