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

Closed (moved)
Open
Opened Jan 07, 2019 by teor@teor

PrivCount proof of concept: implement debugging for PrivCount

Let's debug PrivCount by splitting statistics into multiple categories:

  • public statistics: information that is already public
  • private statistics: information that is sensitive

We can safely log public statistics at any log level. We can publish public statistics' unencrypted, per-relay values and noise amounts in extrainfo descriptors.

We need a debug mode to log private statistics above info level. When we are in debug mode, and not using any public authorities, we can publish private statistics' unencrypted, per-relay values and noise amounts in extrainfo descriptors.

We'll work out other debugging mechanisms during the proof of concept process.

To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
Tor: unspecified
Milestone
Tor: unspecified
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#29007