Opened 8 years ago
Last modified 4 months ago
#7178 new enhancement
NoScript (2.5.7) "reset" button does not use TBB defaults
| Reported by: | Larkdg | Owned by: | tbb-team |
|---|---|---|---|
| Priority: | Low | Milestone: | |
| Component: | Applications/Tor Browser | Version: | |
| Severity: | Normal | Keywords: | tbb-usability, tbb-torbutton, noscript, gitlab-tb-torbutton |
| Cc: | griffin@… | Actual Points: | |
| Parent ID: | Points: | ||
| Reviewer: | Sponsor: |
Description
NoScript (2.5.7) "reset" in TBB (one result)
Debian/Wheezy (updated)
TBB 2.2.39-3 x86_64
TBB default install has NoScript "General" tab "Scripts Globally Allowed" (dangerous) ON and "Appearance" tab "Allow Scripts Globally" (dangerous) ON ... yet a RESET of the add-on sets the first to OFF and the second to ON. Is this normal?
https://trac.torproject.org/projects/tor/ticket/6567
NoScript Needs to be updated. NoScript is now installed by default. Has been discussed. https://lists.torproject.org/pipermail/tor-talk/2012-May/024227.html My conclusion: Disabling it entirely is ok. Disabling on a per domain base is bad for anonymity.
https://trac.torproject.org/projects/tor/ticket/6563
Reinventing the wheel here?
Child Tickets
Change History (7)
comment:1 Changed 8 years ago by
| Keywords: | NoScript 2.5.7 settings reset removed |
|---|---|
| Summary: | NoScript (2.5.7) "reset" in TBB (one result) → NoScript (2.5.7) "reset" button does not use TBB defaults |
comment:2 Changed 8 years ago by
| Keywords: | tbb-usability added |
|---|---|
| Priority: | normal → minor |
comment:3 Changed 6 years ago by
| Component: | TorBrowserButton → Tor Browser |
|---|---|
| Keywords: | tbb-torbutton added |
| Owner: | changed from mikeperry to tbb-team |
comment:4 Changed 6 years ago by
| Cc: | griffin@… added |
|---|
comment:5 Changed 6 years ago by
comment:6 Changed 4 years ago by
| Keywords: | noscript added |
|---|---|
| Severity: | → Normal |
| Version: | Tor: 0.2.2.39 |
Note: See
TracTickets for help on using
tickets.
This would be fairly straightforward to solve if the NoScript codebase were commented. As it stands, hunting down the particular option causing this issue is quite tricky.