Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #17690

Closed (moved)
(moved)
Open
Created 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
Time tracking