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

Closed (moved)
Open
Opened Jul 29, 2018 by teor@teor

Privcount: plan the modules and components

Replying to [26953#comment:3 chelseakomlo]:

Is the idea that this project will remain external to core tor, or will this one day be merged into the core codebase? Definitely having CI in the short term seems wise either way.

That's a good question, nickm and I haven't discussed it yet. And I think we'd benefit from your advice.

For PrivCount in Tor, we need to produce the following components:

  • a Rust "Data Collector" module in Tor that does blinding, encryption, and noise, based on a config
  • a separate "Tally Reporter" binary that does unblinding, decryption, aggregation, and reporting, based on a config
  • some tools for creating and validating configurations

One possible design is:

  • Rust modules for blinding/encryption, noise, aggregation, reporting, and config
  • Glue code and module imports for the Tor Data Collector
  • Application code and module imports for the Tally Reporter
  • Application code and module imports for the tools

Split off https://trac.torproject.org/projects/tor/ticket/26953?replyto=3#comment:3

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#26970