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 313
    • Issues 313
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 34
    • Merge requests 34
  • 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
  • #18918
Closed
Open
Created Apr 28, 2016 by teor@teor

Clarify directory and ORPort checking functions

The OR and dir checking functions in router.c are somewhat confusing. We could document them better, or modify their names, or restructure.

In legacy/trac#18616 (moved), we added:

  • decide_to_advertise_begindir

We already had:

  • check_whether_orport_reachable
  • check_whether_dirport_reachable
  • router_has_bandwidth_to_be_dirserver
  • router_should_be_directory_server
  • dir_server_mode
  • decide_to_advertise_dirport
  • consider_testing_reachability
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking