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

Closed (moved)
Open
Opened Jan 30, 2009 by Roger Dingledine@arma

clients avoid *all* authority types when avoiding any

Clients doing directory fetches avoid authorities of all types when trying to avoid authorities of any type. So a client asking for a v3 consensus will never ask moria2, because moria2 is an authority of some type. Similarly, caches wanting a v3 consensus won't ask moria2, because it's not a v3 authority. Same goes for Tonga, our bridge authority.

See is_trusted = router_digest_is_trusted_dir(status->identity_digest); in router_pick_directory_server_impl() in routerlist.c

We should instead ask if it's a trusted dir for the type of authority we're wondering about.

[Automatically added by flyspray2trac: Operating System: All]

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