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

Closed (moved)
Open
Opened Apr 20, 2013 by bastik@bastik

Update path-specs to educate about family

I'm not sure what Component I should select.

As suggested here: https://lists.torproject.org/pipermail/tor-talk/2013-April/027872.html

based on my email on tor-talk: https://lists.torproject.org/pipermail/tor-talk/2013-April/027869.html

I suggest to update the path-specs with an explanation on how excluding family works.

The dir-specs hold a nice (from my POV) explanation and gives an example.

If two ORs list one another in their "family" entries, then OPs should treat them as a single OR for the purpose of path selection. For example, if node A's descriptor contains "family B", and node B's descriptor contains "family A", then node A and node B should never be used on the same circuit.

The reason I suggest this is because I believe it is to be expected in the path-specs, rather than in the dir-spec. I'm not suggesting to remove it from any other document this explanation is in.

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