Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
A
Analysis
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 19
    • Issues 19
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Members
    • Members
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar

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.

  • The Tor Project
  • Metrics
  • Analysis
  • Issues
  • #29344

Closed
Open
Opened Feb 05, 2019 by Iain Learmonth@irl

Consider heartbeat frequency, logging and extra-info statistics

The heartbeat logging, which includes statistics that we consider sensitive when including them in the extra-info descriptors, captures these statistics at smaller intervals than we do for extra-info descriptors. This is currently enabled by default in both the source distribution and the official Debian packages.

As these are legally discoverable (by virtue of the fact that they exist) we should consider what attacks are enabled and what risk we place on guard/middle relay operators and our users by collecting them.

The statistics have clear engineering value, but it is not clear how much that value degrades when looking at larger intervals.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: tpo/metrics/analysis#29344