Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
T
Tor Browser
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1,512
    • Issues 1,512
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 1
    • Merge Requests 1
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • The Tor Project
  • Applications
  • Tor Browser
  • Issues
  • #40091

Closed
Open
Opened 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
Tor Browser: 10.0
Milestone
Tor Browser: 10.0
Assign milestone
Time tracking
None
Due date
None
Reference: tpo/applications/tor-browser#40091