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

Closed (moved)
Open
Opened Dec 14, 2015 by teor@teor

Tor ignores tunneled connections when checking existing directory downloads

Tor tries to avoid multiple connections to the same directory server to avoid overloading it.

But when checking for existing directory downloads from a server in router_pick_trusteddirserver_impl and router_pick_directory_server_impl, tor ignores connections made via a one-hop ORPort tunnel, and connections made via tor.

This is a hard problem to solve, because ORPort connections can be used for multiple purposes, and can be indirect, so we can't just check the address and port like the existing code does.

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#17848