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

Closed
Open
Opened 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 admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#27475