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,019
    • Issues 1,019
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 3
    • Merge requests 3
  • 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
  • #40091
Closed
Open
Created Aug 19, 2020 by Georg Koppen@gkDeveloper

Move HTTPS Everywhere into omni.ja

At best it is brittle having our HTTPS Everywhere signature exception along with the desired v3 add-on blocklist mechanism. At worst HTTPS Everywhere is broken or disabled.

So, Mozilla engineers recommended putting HTTPS Everywhere into the omni.ja making it a system extension which does not need to be signed.

That's essentially the same path we took for Torbutton and Tor Launcher.

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