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
  • Collapse sidebar
  • Activity
  • Create a new issue
  • 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.

  • Legacy
  • TracTrac
  • Issues
  • #6496

Closed (moved)
Open
Opened Jul 31, 2012 by grarpamp@grarpamp

Relocate HTTPS-E config file (from FF prefs.js)

A default FF prefs.js is around 150 lines. HTTPS-E blows that out with around 1500 more entries, which are expected to grow in number to some fraction of the worlds domains in time. Admins probably don't want to carry optionally installed, and otherwise non-meta extension config like this, in their rolled out prefs.js. And users probably don't want to mess their FF prefs on edit accident. If adblock plus etc can relocate its config, so can HTTPS-E.

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
Reference: legacy/trac#6496