Opened 4 years ago

Last modified 3 months ago

#7532 assigned defect

Count unique IPs in an anonymous way

Reported by: asn Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version: Tor: 0.2.7
Severity: Keywords: research, term-project-ideas, tor-03-unspecified-201612
Cc: Actual Points:
Parent ID: Points: medium
Reviewer: Sponsor: SponsorR-can

Description

Currently, pyobfsproxy (and obfsproxy) keep a list of IPs (or IP hashes) in memory to count connected unique IPs.

Velope suggested that we should find a more privacy-preserving way of counting unique IPs, and he is right.

Aaron suggested to look into https://git.eff.org/?p=cryptolog.git
and nick suggested to "use a bloom filter; count bits; get a probabilistic answer".

Child Tickets

TicketSummaryOwner
#15469Remove data structure containing unique IP address sets

Change History (16)

comment:1 Changed 3 years ago by asn

  • Component changed from pyobfsproxy to Obfsproxy
  • Keywords research added
  • Priority changed from normal to minor

(Moving this to a better component and marking as researchy.)

Would be nice to have. Probably not easy to do; there are various papers on this topic in anonbib.

comment:2 Changed 2 years ago by nickm

  • Milestone set to Tor: 0.2.7.x-final

I met a grad student who has the most marvelous solution for this; I will share the details once I have permission. :)

comment:3 Changed 2 years ago by nickm

(We should use the approach in Tor too!)

comment:4 Changed 2 years ago by asn

  • Component changed from Obfsproxy to Tor
  • Summary changed from Obfsproxy: Count unique IPs in an anonymous way to Count unique IPs in an anonymous way

comment:5 Changed 2 years ago by nickm

  • Owner asn deleted
  • Status changed from new to assigned

comment:6 Changed 2 years ago by nickm

  • Keywords 027-triaged-1-in added

Marking some tickets as triaged-in for 0.2.7 based on early triage

comment:7 Changed 2 years ago by isabela

  • Keywords SponsorR added
  • Points set to medium
  • Priority changed from minor to normal
  • Version set to Tor: 0.2.7

comment:8 Changed 19 months ago by nickm

  • Milestone changed from Tor: 0.2.7.x-final to Tor: 0.2.8.x-final

comment:9 Changed 18 months ago by nickm

  • Keywords SponsorR removed
  • Sponsor set to SponsorR

Bulk-replace SponsorR keyword with SponsorR sponsor field in Tor component.

comment:10 Changed 18 months ago by asn

  • Milestone changed from Tor: 0.2.8.x-final to Tor: 0.2.???

comment:11 Changed 18 months ago by dgoulet

  • Keywords 027-triaged-1-in removed

comment:12 Changed 14 months ago by nickm

  • Keywords 6s194 added

comment:13 Changed 14 months ago by nickm

  • Keywords term-project-ideas added; 6s194 removed

These tickets were tagged "6s194" as ideas for possible term projects for students in MIT subject 6.S194 spring 2016. I'm retagging with term-project-ideas, so that the students can use the 6s194 tag for tickets they're actually working on.

comment:14 Changed 12 months ago by dgoulet

  • Sponsor changed from SponsorR to SponsorR-can

Move those from SponsorR to SponsorR-can.

comment:15 Changed 4 months ago by teor

  • Milestone changed from Tor: 0.2.??? to Tor: 0.3.???

Milestone renamed

comment:16 Changed 3 months ago by nickm

  • Keywords tor-03-unspecified-201612 added
  • Milestone changed from Tor: 0.3.??? to Tor: unspecified

Finally admitting that 0.3.??? was a euphemism for Tor: unspecified all along.

Note: See TracTickets for help on using tickets.