Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar

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.

  • Legacy
  • TracTrac
  • Issues
  • #16909

Closed (moved)
Open
Created Aug 27, 2015 by Georg Koppen@gk

Adapt Tor Browser bundling to new HTTPS-Everywhere ID beginning with 5.1.0

The new AMO signing requires changes to the way we bundle HTTPS-Everyhwere. The good thing is if we use the tags as we did everything is fine signature- and version-wise. The bad thing is the EFF needed to change the ID of the self-hosted HTTPS-Everywhere version due to conflicts on the AMO dashboard.

The other change although orthogonal to the AMO signing is moving to a submodule for the translations. We should verify that our build process picks this up.

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