Skip to content
Snippets Groups Projects
New look: Off

Security level set to "Safest" but JavaScript still Enabled.

    • Closed (moved) Issue created by Trac @tracbot

    TorBrowser 9.0.1 on Whonix.

    Everything worked fine before. When level was set to "Safest" JS was disabled.But now from thin air it started lying. Set to "Safest" but don't block JS. I don't update or somehow mess with torbroswer config. It just started this. I try restarting TorBrowser, Whonix, same issues. Tested on several sites, all says JS enabled.

    Trac:
    Username: tor70001

    To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information

    Child items ...

    • Activity

    • Trac added component::applications/tor browser noscript owner::tbb-team priority::medium reporter::tor70001 severity::normal status::new type::defect labels

      added component::applications/tor browser noscript owner::tbb-team priority::medium reporter::tor70001 severity::normal status::new type::defect labels

    • Trac
      Trac @tracbot ·
      Author

      Trac:
      Username: tor70001

      js

    • Trac
      Trac @tracbot ·
      Author

      screenshot

      Trac:
      Username: tor70001

    • Pili Guerra
      Pili Guerra @pili ·

      I can't reproduce this with 9.5a2...

      Can someone else on whonix and 9.0.1 try to reproduce?

    • C
      cypherpunks @cypherpunks ·

      Unfortunately, this is not just somebody's weird settings. Seen this on Windows. Switching to Safer and back seems to fix it, but the root cause is still unknown :(

    • Pili Guerra
      Pili Guerra @pili ·

      Does this happen every time or only from the second time the browser has been started? If so, it could be related to #31094 (moved)

      Also, what happens if you download Tor Browser from our website directly? Does this behaviour still happen?

    • C
      cypherpunks @cypherpunks ·

      Oh shit! It happens again! And the console is full of:

      [NoScript] Policy was undefined, retrying in 1/2 sec... log.js:7:13
Error while fetching policy <unavailable> staticNS.js:56:21

      (move it to the Tor Browser component at least)

    • C
      cypherpunks @cypherpunks ·

      Okay, got it. This is a NoScript can't update itself sanely, so that all Tor Browsers updated to NoScript 11.0.9 are destroyed:

      [11-22 05:22:18] Torbutton INFO: controlPort >> 650 STREAM 1194 FAILED 993 255.255.255.255:443 REASON=END REMOTE_REASON=NOROUTE
[11-22 05:22:18] Torbutton INFO: controlPort >> 650 STREAM 1194 CLOSED 993 255.255.255.255:443 REASON=END REMOTE_REASON=NOROUTE
Tor NOTICE: Have tried resolving or connecting to address '[scrubbed]' at 3 different places. Giving up.
<unavailable> SyncMessage.js:216:21

      ticket:32549#comment:1

    • Roger Dingledine
      Roger Dingledine @arma ·

      Trac:
      Owner: N/A to tbb-team
      Component: Applications to Applications/Tor Browser
      Severity: Critical to Normal
      Priority: Immediate to Medium

    • S
      Matthew Finkel @sysrqb ·

      Cypherpunk, are there steps for reproducing this or does it seem random?

      Trac:
      Keywords: N/A deleted, noscript added
      Cc: N/A to ma1

    • C
      cypherpunks @cypherpunks ·

      Just refreshed https://blog.torproject.org/ after hibernation and got again:

      [11-27 04:03:27] Torbutton INFO: tor SOCKS: https://255.255.255.255/moz-extension://[NS UUID]%2Chttps%3A%2F%2Fblog.torproject.org%2F&url=https%3A%2F%2Fblog.torproject.org%2F&top=true&suspend=true via
                       torproject.org:bd3c437faec67f5a4d99a05f1db64101
[11-27 04:03:27] Torbutton INFO: controlPort >> 650 STREAM 468 NEW 0 255.255.255.255:443 SOURCE_ADDR=127.0.0.1:52645 PURPOSE=USER
[11-27 04:03:27] Torbutton INFO: controlPort >> 650 STREAM 468 SENTCONNECT 81 255.255.255.255:443
Error: Could not establish connection. Receiving end does not exist. SyncMessage.js:193:25
[11-27 04:03:28] Torbutton INFO: controlPort >> 650 STREAM 468 DETACHED 81 255.255.255.255:443 REASON=END REMOTE_REASON=NOROUTE
...
    • C
      cypherpunks @cypherpunks ·

      Finally, clean new installation of torbrowser-install-9.0.1_en-US.exe reproduces this behavior after several hibernations. Priority: Immediate → Medium Severity: Critical → Normal Revert!

    • C
      cypherpunks @cypherpunks ·

      Unfortunately, clean new installation of torbrowser-install-9.0.2_en-US.exe with NoScript 11.0.9 integrated and no updates started to show the same behavior today :( So, it's not an update bug, but NoScript is totally broken!

    • C
      cypherpunks @cypherpunks ·

      New Identity doesn't fix the issue, but Restart does: looks like some sort of race condition, so the problem could be on your side.

    • C
      cypherpunks @cypherpunks ·

      Unfortunately, this is not just somebody's weird settings. Seen this on Windows. Switching to Safer and back seems to fix it, but the root cause is still unknown :( Doesn't work for me. Switching levels just gives:

      No matching message handler for the given recipient. 2 MessageChannel.jsm:964
    _handleMessage resource://gre/modules/MessageChannel.jsm:964
    • A
      adrelanos @adrelanos ·

      Is this related to the noscript default whitelist? (#31798 (moved)) I.e. just some pages such as google.com are white listed or is javascript allowed?

    • C
      cypherpunks @cypherpunks ·

      No, it is not related.

      It is a shame that tbb-team doesn't give a shit about it for more than a month!

      NoScript is auto-updated to 11.0.10, so that the testing should be restarted from the beginning with the new version, but setting extensions.webextensions.remote to false seems to be a workaround so far...

    • C
      cypherpunks @cypherpunks ·

      Clean new torbrowser-install-9.0.4_en-US.exe and the same shit. Is somebody going to fix it?

    • C
      cypherpunks @cypherpunks ·

      Huh, it also has a sex with CPU when a new tab is opened:

      Error while fetching policy <unavailable> staticNS.js:56:21
[NoScript] Policy was undefined, retrying in 1/2 sec... log.js:7:13
Error while fetching policy <unavailable> staticNS.js:56:21
[NoScript] Policy was undefined, retrying in 1/2 sec... log.js:7:13
Error while fetching policy <unavailable> staticNS.js:56:21
[NoScript] Policy was undefined, retrying in 1/2 sec... log.js:7:13
Error while fetching policy <unavailable> staticNS.js:56:21
[NoScript] Policy was undefined, retrying in 1/2 sec... log.js:7:13
Error while fetching policy <unavailable> staticNS.js:56:21
[NoScript] Policy was undefined, retrying in 1/2 sec... log.js:7:13
Error while fetching policy <unavailable> staticNS.js:56:21
[NoScript] Policy was undefined, retrying in 1/2 sec... log.js:7:13
Error while fetching policy <unavailable> staticNS.js:56:21
[NoScript] Policy was undefined, retrying in 1/2 sec... log.js:7:13
Error while fetching policy <unavailable> staticNS.js:56:21
[NoScript] Policy was undefined, retrying in 1/2 sec... log.js:7:13
Error while fetching policy <unavailable> staticNS.js:56:21
[NoScript] Policy was undefined, retrying in 1/2 sec... log.js:7:13
Error while fetching policy <unavailable> staticNS.js:56:21
[NoScript] Policy was undefined, retrying in 1/2 sec... log.js:7:13
Error while fetching policy <unavailable> staticNS.js:56:21
[NoScript] Policy was undefined, retrying in 1/2 sec... log.js:7:13
Error while fetching policy <unavailable> staticNS.js:56:21
[NoScript] Policy was undefined, retrying in 1/2 sec... log.js:7:13
Error while fetching policy <unavailable> staticNS.js:56:21
[NoScript] Policy was undefined, retrying in 1/2 sec... log.js:7:13
Error while fetching policy <unavailable> staticNS.js:56:21
[NoScript] Policy was undefined, retrying in 1/2 sec... log.js:7:13
Error while fetching policy <unavailable> staticNS.js:56:21
[NoScript] Policy was undefined, retrying in 1/2 sec... log.js:7:13
Error while fetching policy <unavailable> staticNS.js:56:21
[NoScript] Policy was undefined, retrying in 1/2 sec... log.js:7:13
Error while fetching policy <unavailable> staticNS.js:56:21
[NoScript] Policy was undefined, retrying in 1/2 sec... log.js:7:13
Error while fetching policy <unavailable> staticNS.js:56:21
[NoScript] Policy was undefined, retrying in 1/2 sec... log.js:7:13
Error while fetching policy <unavailable> staticNS.js:56:21
[NoScript] Policy was undefined, retrying in 1/2 sec... log.js:7:13
Error while fetching policy <unavailable> staticNS.js:56:21
[NoScript] Policy was undefined, retrying in 1/2 sec... log.js:7:13
Error while fetching policy <unavailable> staticNS.js:56:21
[NoScript] Policy was undefined, retrying in 1/2 sec... log.js:7:13
Error while fetching policy <unavailable> staticNS.js:56:21
[NoScript] Policy was undefined, retrying in 1/2 sec... log.js:7:13
Error while fetching policy <unavailable> staticNS.js:56:21
[NoScript] Policy was undefined, retrying in 1/2 sec... log.js:7:13
Error while fetching policy <unavailable> staticNS.js:56:21
[NoScript] Policy was undefined, retrying in 1/2 sec... log.js:7:13
Error while fetching policy <unavailable> staticNS.js:56:21
[NoScript] Policy was undefined, retrying in 1/2 sec... log.js:7:13
Error while fetching policy <unavailable> staticNS.js:56:21
[NoScript] Policy was undefined, retrying in 1/2 sec... log.js:7:13
    • C
      cypherpunks @cypherpunks ·

      aaaaaaaaaaaand, finally: the bug is that Firefox doesn't restart dead WebExtensions Remote process!

    • C
      cypherpunks @cypherpunks ·

      Thanks to some changes in NoScript, it no longer crashes WebExtensions Remote process. Thanks to #33613 (moved), it disables JavaScript execution, as a safe guard, when Firefox doesn't restart dead WebExtensions Remote process. Only #32549 (moved) remains in that situation.

    • cypherpunks mentioned in issue #32549 (moved)

      mentioned in issue #32549 (moved)

    • Trac moved to tpo/applications/tor-browser#32536 (closed)

      moved to tpo/applications/tor-browser#32536 (closed)

    Please register or sign in to reply