Opened 8 years ago

Closed 2 years ago

#4688 closed defect (fixed)

control-spec doesn't specify rounding for status/clients-seen

Reported by: atagar Owned by:
Priority: Low Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords: tor-relay
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

10:38 < skep> hello, i have a question about a specific torbridge command. If I use the "GETINFO status/clients-seen" (via telnet) I get a CountrySummary. So far so good..but why are the numbers there only in steps of 8? I looked through the documentation, but can't figure it out..
10:44 < atagar> skep: iirc status/clients-seen provides just daily counts and might also rounding the results (if the later's the case then I don't recall the reasoning for it and it's a bug that it's missing from the spec)
10:46 < skep> I guess i will look into the code..maybe i can figure it out why only in such steps..thanks anyway
10:46 < wseltzer> skep: see metrics.torproject.org/papers/wecsr10.pdf for the rationale
10:46 < skep> ah..thanks
10:46 < wseltzer> there's a concern that precise numbers could deanonymize users

I'll need to think some more about if I agree that the fuzzing is useful here or not. Arm provides this metric too without fuzzing or the daily aggregation since I both didn't see the harm nor know that tor did this.

Cheers! -Damian

PS. The reason for me to get the metric myself rather than use GETINFO is that status/clients-seen only works for bridges, not fuzzing.

Child Tickets

Change History (4)

comment:1 Changed 7 years ago by nickm

Milestone: Tor: unspecified

comment:2 Changed 7 years ago by nickm

Keywords: tor-relay added

comment:3 Changed 7 years ago by nickm

Component: Tor RelayTor

comment:4 Changed 2 years ago by nickm

Resolution: fixed
Severity: Normal
Status: newclosed

Added a note and a pointer to the algorithm in c07abd047db5f8

Note: See TracTickets for help on using tickets.