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

Closed (moved)
Open
Opened Feb 15, 2013 by Roger Dingledine@arma

Hidden services should try harder to reuse their old intro points

The current hidden service behavior is that when Tor loses its intro circuits, it chooses new intro points and makes new circuits to them -- which means anybody who has the old hidden service descriptor is going to be introducing herself to the wrong intro points.

If our intro circuits close, but it was because our network failed and not because the intro points failed, we should reestablish new intro circuits to the old intro points.

Nathan wants this for running hidden services on Orbot, since Orbot users change networks (and thus lose existing circuits) quite often.

I expect the main tricky point to be distinguishing "network failed" from "intro point failed". I wonder if some of our CBT work is reusable here.

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