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 319
    • Issues 319
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 37
    • Merge requests 37
  • 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
  • #17848
Closed
Open
Created 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 an admin enable hashed storage. More information
Assignee
Assign to
Time tracking