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

Closed (moved)
Open
Opened Apr 09, 2018 by Mike Perry@mikeperry

Check/enforce path restrictions for each path position

For the vanguard torrc options, we may want to check that each layer has at least one node from a different /16 and different node family than others in that layer, to ensure that a path can always be built using the vanguard set.

We may also want to do the same thing for Tor's Primary Guard set from Prop271, to ensure that an adversary can't force the user to pick guards randomly from Sampled Guards.

Doing both of these things at once should allow us to drop #24487 (moved).

See also: https://gitweb.torproject.org/torspec.git/tree/proposals/291-two-guard-nodes.txt#n33

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