Skip to content
GitLab
Projects Groups Topics 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
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #27475
Closed
Open
Issue created Sep 05, 2018 by Damian Johnson@atagar

Scrub connection info for any non-relay

Nyx attempts to be a bit too smart with its 'should I scrub connection info?' check. As teor points out there's quite a few scenarios where this can go wrong...

https://lists.torproject.org/pipermail/tor-relays/2018-September/016153.html

Presently the check is 'scrub the connection if it isn't in the consensus and I'm a bridge, guard, or exit'. We should drop this second clause (ie. scrub anything not in the consensus).

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