PrivCount proof of concept with existing statistics
Let's implement a proof-of-concept implementation of PrivCount that adds some noise to existing relay statistics, and then aggregates them.
This proof of concept will help us answer open questions, find bugs and unexpected issues, and get started on the metrics analysis. (But it doesn't need to be secure, because the stats are already public for each relay.)
Child Tickets
Ticket | Status | Owner | Summary | Component |
---|
#27161 | assigned | | Add make check-rustfmt to make check | Core Tor/Tor |
#29004 | new | | PrivCount proof of concept: implement check counters | Core Tor/Tor |
#29005 | new | | PrivCount proof of concept: implement consumed bandwidth counters | Core Tor/Tor |
#29006 | assigned | | PrivCount proof of concept: add noise to counters | Core Tor/Tor |
#29007 | assigned | | PrivCount proof of concept: implement debugging for PrivCount | Core Tor/Tor |
#29008 | assigned | | PrivCount proof of concept: add a PrivCount module, torrc option, and protocol | Core Tor/Tor |
#29009 | new | | PrivCount proof of concept: use blinding and Shamir secret sharing | Core Tor/Tor |
#29010 | new | | PrivCount proof of concept: work out how to do CI for PrivCount using chutney | Core Tor/Tor |
#29011 | closed | | PrivCount proof of concept: work out how to do integration testing without chutney | Core Tor/Tor |
#29129 | new | | PrivCount proof of concept: decide if we want to remove bandwidth statistics | Core Tor/Tor |
#29265 | new | | PrivCount proof of concept: Re-implement the C code in Rust | Core Tor/Tor |
#29266 | new | | PrivCount proof of concept: round results to hide usage over time | Core Tor/Tor |
#29268 | new | | PrivCount proof of concept: Use the subsystems API for PrivCount | Core Tor/Tor |
#29271 | new | | PrivCount proof of concept: use pubsub for events that PrivCount cares about | Core Tor/Tor |
Change History (18)
Milestone: |
Tor: unspecified →
Tor: 0.3.6.x-final
|
Keywords: |
privcount added
|
Milestone: |
Tor: 0.3.6.x-final →
Tor: 0.4.0.x-final
|
Keywords: |
040-unreached-20190109 041-proposed added
|
Milestone: |
Tor: 0.4.0.x-final →
Tor: unspecified
|
Keywords: |
041-proposed-on-roadmap added; 041-proposed removed
|
Milestone: |
Tor: unspecified →
Tor: 0.4.1.x-final
|
Keywords: |
041-accepted-20190115 added; 041-proposed-on-roadmap removed
|
Keywords: |
network-team-roadmap-2019-Q1Q2 added
|
Milestone: |
Tor: 0.4.1.x-final →
Tor: 0.4.2.x-final
|
Milestone: |
Tor: 0.4.2.x-final →
Tor: unspecified
|
Status: |
assigned →
new
|
We want to create a local proof of concept with counters set to 0 and 1. Then we want to create a minimal viable product with the relay bandwidth statistic. (If we want to show Guard, Middle, and Exit bandwidth, we'll need to make this statistic a histogram.)
Some of our detailed planning is here:
https://trac.torproject.org/projects/tor/wiki/org/meetings/2018MexicoCity/Notes/PrivCount