Opened 9 months ago

Last modified 6 months ago

#33325 new project

O2.3 Implement static guard node support for OnionPerf.

Reported by: gaba Owned by: metrics-team
Priority: Medium Milestone:
Component: Metrics/Onionperf Version:
Severity: Normal Keywords: metrics-team-roadmap-2020
Cc: acute Actual Points:
Parent ID: #33322 Points:
Reviewer: Sponsor: Sponsor59


Tor clients generally make three-hop circuits (that is, paths that go through three relays). The first position in the path called the guard node and is always chosen as the first hop for a fixed period of time. Using static guard nodes help protect against a certain kind of anonymity-breaking attack. The long-running OnionPerf instances that are currently deployed do not implement this mitigation because choosing a static guard at setup time would heavily influence their measured performance. Instead, they’re configured not to choose a guard for each measurement. We want to be able to measure the effects of good, bad, or average guards and compare the results, which is not possible without the opportunity to select a static guard node for an OnionPerf instance. Implementing the option to use a static guard in future OnionPerf instances will allow us to measure Tor performance closer to how clients experience it.

Child Tickets

#33399acceptedkarstenMeasure static guard nodes with OnionPerfMetrics/Onionperf
#33419closedmetrics-teamAdd analysis to support static guard measurementsMetrics/Onionperf

Change History (2)

comment:1 Changed 8 months ago by gaba

Sponsor: Sponsor59

comment:2 Changed 6 months ago by gaba

Keywords: metrics-team-roadmap-2020 added

OnionPerf project will be the main metrics project for 2020.

Note: See TracTickets for help on using tickets.