Opened 2 years ago

Last modified 3 months ago

#22898 new task

Help get privcount standardized and merged

Reported by: nickm Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords: 035-roadmap-master, 035-triaged-in-20180711, 041-proposed
Cc: amj703 Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description (last modified by teor)

This would fit nicely with our sponsor Q work.

Edit: The project page is at:
https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/PrivCountInTor

Child Tickets

TicketStatusOwnerSummaryComponent
#15272newThink of more research questions that we can answer with statisticsCore Tor/Tor
#22729newRevisit relay read/write history resolution (for onion services)Core Tor/Tor
#23147closedteorprop288: Merge privcount-in-tor data collector backend implementationCore Tor/Tor
#25153assignedSpecify how PrivCount in Tor statistics are configured and interpretedCore Tor/Tor
#25263assignedFix the hidden service statistics noise (and the privcount noise by extension)Core Tor/Tor
#26637newPrivcount noise generation implemented and deployedCore Tor/Tor
#26904newWork out if we need to round scanner measured bandwidths to protect individual client usageCore Tor/Tor
#26905newWork out if we need to round observed relay bandwidths to protect individual client usageCore Tor/Tor
#26970assignedPrivcount: plan the modules and componentsCore Tor/Tor
#27908assignedPrivCount proof of concept with existing statisticsCore Tor/Tor
#29130newWork out how to handle multiple reports from the same relay in PrivCountCore Tor/Tor
#29270newWork out the config and control interfaces to PrivCountCore Tor/Tor
#29317newProtect heartbeat logs using PrivCountCore Tor/Tor

Change History (14)

comment:1 Changed 19 months ago by teor

Milestone: Tor: unspecifiedTor: 0.3.4.x-final
Type: defecttask

comment:2 Changed 17 months ago by nickm

Keywords: 034-triage-20180328 added

comment:3 Changed 17 months ago by nickm

Keywords: 034-removed-20180328 added

Per our triage process, these tickets are pending removal from 0.3.4.

comment:4 Changed 17 months ago by nickm

Milestone: Tor: 0.3.4.x-finalTor: 0.3.5.x-final

This merge will start in 0.3.4, but finish in 0.3.5 (IIUC)

Last edited 17 months ago by nickm (previous) (diff)

comment:5 Changed 14 months ago by nickm

Keywords: 035-roadmap-master added; 034-triage-20180328 034-removed-20180328 removed

comment:6 Changed 14 months ago by teor

Description: modified (diff)

Add link to project page

comment:7 Changed 14 months ago by nickm

Keywords: 035-triaged-in-20180711 added

comment:8 Changed 13 months ago by nickm

Sponsor: SponsorQ-canSponsorV-can

comment:9 Changed 12 months ago by nickm

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

Deferring privcount tickets in 0.3.5 to 0.3.6

comment:10 Changed 10 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:11 Changed 7 months ago by amj703

Cc: amj703 added

comment:12 Changed 7 months ago by nickm

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

Mark some 0.4.0.x tickets as proposed for 0.4.1.x

comment:13 Changed 3 months ago by gaba

Removing sponsor V as we do not have more time to include this tickets in the sponsor.

comment:14 Changed 3 months ago by gaba

Sponsor: SponsorV-can

Removing sponsor from tickets that we do not have time to fit in the remain of this sponsorship.

Note: See TracTickets for help on using tickets.