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
  • #18749

Closed (moved)
Open
Opened Apr 07, 2016 by teor@teor

Consider only including one fallback per operator

If we have a large number of fallback directory mirrors, we could make sure each operator only sees a small proportion of traffic by only including one fallback per operator.

We could identify operators by:

  • Contact Info
  • My Family

However, this is easy to break, because it only works for operators who correctly configure MyFamily, or use identical ContactInfo fields. (That said, these operators can still have their machines compromised.)

As a workaround, in #17158 (moved) I modified the script to output the number of fallbacks per ContactInfo. This will note in each fallback entry if an operators could see a large amount of client traffic.

To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
Tor: 0.2.8.x-final
Milestone
Tor: 0.2.8.x-final
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#18749