Opened 4 months ago

Last modified 8 days ago

#27908 assigned task

PrivCount proof of concept with existing statistics

Reported by: teor Owned by: teor
Priority: Medium Milestone: Tor: 0.4.1.x-final
Component: Core Tor/Tor Version:
Severity: Normal Keywords: privcount, 040-unreached-20190109, 041-accepted-20190115
Cc: amj703 Actual Points:
Parent ID: #22898 Points: 3
Reviewer: Sponsor: SponsorV

Description

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

TicketStatusOwnerSummaryComponent
#29004needs_revisionteorPrivCount proof of concept: implement check countersCore Tor/Tor
#29005assignedteorPrivCount proof of concept: implement consumed bandwidth countersCore Tor/Tor
#29006assignedteorPrivCount proof of concept: add noise to countersCore Tor/Tor
#29007assignedteorPrivCount proof of concept: work out how to debug PrivCountCore Tor/Tor
#29008assignedteorPrivCount proof of concept: add a PrivCount module, torrc option, and protocolCore Tor/Tor
#29009newPrivCount proof of concept: use blinding and Shamir secret sharingCore Tor/Tor
#29010assignedteorPrivCount proof of concept: work out how to do CI for PrivCount using chutneyCore Tor/Tor
#29011newPrivCount proof of concept: work out how to do integration testing without chutneyCore Tor/Tor
#29129newPrivCount proof of concept: decide if we want to remove bandwidth statisticsCore Tor/Tor

Change History (11)

comment:1 Changed 4 months ago by nickm

Milestone: Tor: unspecifiedTor: 0.3.6.x-final

comment:2 Changed 4 months ago by teor

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

comment:3 Changed 3 months ago by gaba

Sponsor: SponsorV

comment:4 Changed 3 months ago by gaba

Keywords: privcount added

comment:5 Changed 3 months ago by nickm

Milestone: Tor: 0.3.6.x-finalTor: 0.4.0.x-final

Tor 0.3.6.x has been renamed to 0.4.0.x.

comment:6 Changed 2 weeks ago by teor

Type: enhancementtask

This can be a parent task

comment:7 Changed 2 weeks ago by teor

Keywords: 040-unreached-20190109 041-proposed added
Milestone: Tor: 0.4.0.x-finalTor: unspecified

These tasks are on the 0.4.1 roadmap for PrivCount and Sponsor V.

comment:8 Changed 2 weeks ago by teor

Keywords: 041-proposed-on-roadmap added; 041-proposed removed
Milestone: Tor: unspecifiedTor: 0.4.1.x-final

Let's review these tickets at the next meeting using our 041-proposed process.

They're on the roadmap, so the review should focus on ticket size and team capacity (and sponsor expectations).

comment:9 Changed 9 days ago by teor

Points: 3

The points for this ticket are for the remaining sub tasks that we haven't created yet,

comment:10 Changed 9 days ago by amj703

Cc: amj703 added

comment:11 Changed 8 days ago by teor

Keywords: 041-accepted-20190115 added; 041-proposed-on-roadmap removed

These PrivCount tickets are on the 041 roadmap, we accepted their points estimates in 041 without discussion.

Note: See TracTickets for help on using tickets.