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
  • Activity
  • Create a new issue
  • 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.

  • Legacy
  • TracTrac
  • Issues
  • #23481

Closed (moved)
Open
Opened Sep 12, 2017 by David Goulet@dgoulet😈

hs-v3: Client fails to reach service before 90% bootstrap

It appears that between bootstrap 85% and 90%, it is when the consensus is fetch and we wait on it before trying to establish a first circuit which would bring us to 90%.

Before that, we have no live consensus so setting the hsdir index to a node_t fails because it requires a live consensus to do so. Because of that, a client just can't reach any service because it can not build an hashring.

I think we should require any client actions to have a live consensus which would mean to either stall the SOCKS request until we have it (seems to be around 90% bootstrap) or we close it right away and ask to come back later.

I would go for stalling and try once the live consensus is here.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Tor: 0.3.2.x-final
Milestone
Tor: 0.3.2.x-final
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#23481