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

Closed (moved)
Open
Opened Jun 25, 2011 by Robert Ransom@rransom

Replay-detection window for HS INTRODUCE2 cells causes HS reachability failures

Currently, hidden services only accept a v3 INTRODUCE2 cell from a client if the timestamp it contains is within 30 minutes of the service's current time, so that the service doesn't need to keep entries in its replay-detection cache for very long. We should expand that window.

But in order to figure out how large the window should be, we need some statistics for how many entries are stored in a popular hidden service's replay cache. We should also investigate the typical lifetimes of HS descriptors and service-side introduction-point circuits, to find out whether we can remove the timestamp check entirely.

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