Skip to content
GitLab
Projects Groups Snippets
  • /
  • 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
  • #17857
Closed (moved) (moved)
Open
Issue created Dec 15, 2015 by teor@teor

Create a consensus param to disable (netflow) padding if RSOS is enabled

Because RSOS and Proposal 252 both appear to cause an onion service to make a lot of orconns to many relays, the total overhead of the netflow padding defense will be much larger for these services.

In an ideal world, we'd find some way to minimize the number of orconns that these services make, because the increased level of connection multiplexing would be better against traffic analysis attacks, and thus also mean less overhead for padding defenses (including netflow padding, but beyond that as well).

In the meantime, however, we should provide the ability to disable netflow padding via the consensus for these services. With a consensus param, we can monitor the netflow padding overhead in relay extra-info descriptors, and experiment with turning padding for RSOS/SOS on and off while observing the change in total overhead at relays.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking