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

Closed (moved)
Open
Opened Jan 12, 2018 by teor@teor

Directory Authorities should test reachability of relays in their family

Sebastian reported on #tor-dev that directory authorities can't set MyFamily, because it makes the relays in the family get marked as not Running.

I'm not sure if this restriction is in the connecting code on authorities or relays, or the accepting code on relays.

If it's on the connecting side, we can disable it on authorities.

If it is in the accepting code on relays, maybe we need to keep it as a defence in depth measure. But we could disable it for authority IP addresses. (It wouldn't work with multiple authority IPs or OutboundBindAddress, but that's getting obscure.)

To upload designs, you'll need to enable LFS and have 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#24876