Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • T Tor Browser
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1,286
    • Issues 1,286
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 6
    • Merge requests 6
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Applications
  • Tor Browser
  • Issues
  • #13937
Closed
Open
Created Dec 10, 2014 by Peter Eckersley@pde

Allow the use of NoScript in whitelist mode

TBB customises NoScript to only allow a simple toggle between global allow / global deny of scripts. That's a reasonable attempt to make a hard-to-use tool more comprehensible for many types of users.

Power users however have good reasons to want NoScript's default whitelist-based UI instead. For instance, a user may wish to allow Google JS in order to be able to solve CAPTCHAs and use Google's search engine, but not want to take the risks of JS-dependent vulnerabilities on every other site they visit with TBB.

Currently there doesn't seem to be a way to make that happen in the TBB NoScript UI.

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