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

Closed (moved)
Open
Opened Nov 25, 2015 by George Kadianakis@asn

prop224: Control the number of HSDirs using a consensus parameter

People are worrying that HSDirs can launch traffic confirmation attacks against hidden service clients. This will be harder to do after the shared randomness proposal gets deployed but still not impossible (without some sort of PIR scheme).

Till we get there, Roger suggested we make the number of HSDirs configurable, and control it using a consensus parameter (similar to how we use NumEntryGuards).

This will also be useful after prop#246 gets implemented and we merge HSDirs with IPs.

On the technical side, we might need two consensus parameters. One for the number of replicas, and one for the number of descriptors per replica.

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#17690