Opened 3 years ago

Last modified 12 months ago

#22729 new defect

Revisit relay read/write history resolution (for onion services)

Reported by: mikeperry Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords: tor-hs, guard-discovery-stats, privcount
Cc: karsten Actual Points:
Parent ID: #22898 Points:
Reviewer: Sponsor:


At Wilmington, we wondered if we still were providing too fine-grained information in the read-write statistics, and if we should add noise there or reduce the reporting frequency.

It would be good to put bounds on the resolution, frequency, and noise we want here, as this would also help us decide what to do about things like #22422.

Child Tickets

Change History (10)

comment:1 Changed 3 years ago by mikeperry

See #23512 for an instance where these stats revealed too much information and aided in a deanonymization attack.

comment:2 Changed 3 years ago by mikeperry

Keywords: guard-discovery-stats added; guard-discovery removed

comment:3 Changed 3 years ago by mikeperry

Milestone: Tor: unspecified

comment:4 Changed 22 months ago by mikeperry

For reference, we did in fact raise our stats reporting interval to 24 hours for bandwidth stats. This ticket is about determining if that is enough.

comment:5 Changed 22 months ago by mikeperry

Component: Core Tor/TorDNSELCore Tor/Tor

comment:6 Changed 17 months ago by teor

Keywords: privcount added
Sponsor: SponsorV-can

We should think about this as part of PrivCount.

comment:7 Changed 17 months ago by teor

Parent ID: #22898

comment:8 Changed 13 months ago by mikeperry

In ticket:23512#comment:35, jaym reported that after the fix, write totals were larger than read totals for relays under attack by the oom side channel.

There are many possible sources for this discrepancy, and it may not actually not be visible under our current live network's stats resolution -- the discrepancy was shown only in chutney. We should see if we can reproduce it using his code at in a more realistic fashion

comment:9 Changed 12 months ago by gaba

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

comment:10 Changed 12 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.