[tor-bugs] #27881 [- Select a component]: NoScript initial configuration bug?
Tor Bug Tracker & Wiki
blackhole at torproject.org
Thu Sep 27 05:34:26 UTC 2018
#27881: NoScript initial configuration bug?
------------------------+--------------------------------------
Reporter: simplestuf | Owner: (none)
Type: defect | Status: new
Priority: Medium | Component: - Select a component
Version: | Severity: Normal
Keywords: | Actual Points:
Parent ID: | Points:
Reviewer: | Sponsor:
------------------------+--------------------------------------
I'm using Tor Browser 8.0.1 (based on Mozilla Firefox 60.2.0esr) (64-bit),
on OSX Yosemite 10.10.5.
When I open Tor Browser, go to the Add-ons Manager, and then open NoScript
preferences; the starting configuration under the General Tab is *always*:
To have *everything* enabled for the "DEFAULT" Preset customization
(script, object, media, frame, font, webgl, fetch, other).
To have *everything* enabled for the "TRUSTED" Preset customization.
To have only media, frame and font enabled for the "UNTRUSTED" Preset
customization.
The per-site permissions list is also empty.
After pressing the 'Reset' button:
I have frame, fetch and other enabled under "DEFAULT"
I have everything enabled under "TRUSTED"
I have nothing enabled under "UNTRUSTED"
I have a whole bunch of per-site permissions being included.
Regardless of whether Reset is pressed, or whether I adjust the settings
myself, whenever Tor Browser is reopened, the same insecure initial
configuration always reappears.
Only after permanently disabling the file download warning, I am able to
export a NoScript configuration, and Import the generated file again after
startup to return NoScript to my preferred settings. As always, the
starting configuration after Tor Browser restart is the insecure state
described above.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/27881>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
More information about the tor-bugs
mailing list