Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
T
Tor
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1,082
    • Issues 1,082
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 27
    • Merge Requests 27
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • 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.

  • The Tor Project
  • Core
  • Tor
  • Issues
  • #40287

Closed
Open
Created Feb 10, 2021 by Roger Dingledine@armaReporter

Dir auths should stop testing reachability of their DirPort

This is the tiny piece of #40282 (closed) that needs to be done soon: we've put patches in place so that relays won't allow exiting to the listed dir auth dirports, yet the dir auths use exactly this technique to test their reachability, and they currently don't publish their descriptor if they can't find their dirport reachable.

This surprise happened in practice during the "dirport ddos via exits" event, where moria1 kept complaining that its dirport wasn't reachable, and I assume that meant it wasn't ever planning to publish a new descriptor, which meant it would eventually fall out of the consensus (which isn't the end of the world either, since it doesn't need to be in the consensus for most of its functions).

If we were doing #40282 (closed) in 0.4.5 and doing the "leave the dirport listed but just stop testing it" version of that ticket, we could just do that and it would accomplish this ticket too. But my guess is that we want to do that ticket for 0.4.6, in which case we need to do some minimal thing in 0.4.5 before we get there?

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Tor: 0.4.5.7-stable
Milestone
Tor: 0.4.5.7-stable (Past due)
Assign milestone
Time tracking
None
Due date
None