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

Closed (moved)
Open
Opened Jan 25, 2019 by Trac@tracbot

Onion service can do self-reachability tests to detect overwhelmed guards

For the current Tor protocol, hidden services connect into Tor network only through one Guard node (Vanguard is not running on default). As a result, all the HS-IntroPoint circuit of the hidden service are all using one guard. As we all know, the HS-IntroPoint is quite special on its cell sequence, so the malicious guard relays can drop all the incoming cells of HS-IntroPoint until the hidden service rebuild its HS-IntroPoint circuit. And the malicious guard can attack the new circuits again. Because the incoming cells of HS-IntroPoint circuit (introduce1 cells) are all droped, so the hidden services cannot be accessed by any user, and eclipsed by its Guard relay.

This mater is appearing after reduce the number of guards to one, and if the hidden service not run the vangard, the hidden service has the risk of being eclipsed.

Trac:
Username: TBD.Chen

To upload designs, you'll need to enable LFS and have an 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#29174