Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Tor Tor
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 832
    • Issues 832
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 31
    • Merge requests 31
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Core
  • TorTor
  • Issues
  • #24876

Closed
Open
Created 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 an admin enable hashed storage. More information
Assignee
Assign to
Time tracking