Opened 5 years ago

Last modified 3 months ago

#7532 new defect

Count unique IPs in an anonymous way

Reported by: asn Owned by: asn
Priority: Medium Milestone: Tor: unspecified
Component: Obfuscation/Obfsproxy Version: Tor: 0.2.7
Severity: Normal Keywords: research, term-project-ideas maybe-bad-idea needs-discussion
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

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

TicketStatusOwnerSummaryComponent
#15469newRemove data structure containing unique IP address setsCore Tor/Tor

Change History (20)

comment:1 Changed 3 years ago by asn

Component: pyobfsproxyObfsproxy
Keywords: research added
Priority: normalminor

(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 3 years ago by nickm

Milestone: 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 3 years ago by nickm

(We should use the approach in Tor too!)

comment:4 Changed 2 years ago by asn

Component: ObfsproxyTor
Summary: Obfsproxy: Count unique IPs in an anonymous wayCount unique IPs in an anonymous way

comment:5 Changed 2 years ago by nickm

Owner: asn deleted
Status: newassigned

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: medium
Priority: minornormal
Version: Tor: 0.2.7

comment:8 Changed 2 years ago by nickm

Milestone: Tor: 0.2.7.x-finalTor: 0.2.8.x-final

comment:9 Changed 23 months ago by nickm

Keywords: SponsorR removed
Sponsor: SponsorR

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

comment:10 Changed 23 months ago by asn

Milestone: Tor: 0.2.8.x-finalTor: 0.2.???

comment:11 Changed 23 months ago by dgoulet

Keywords: 027-triaged-1-in removed

comment:12 Changed 19 months ago by nickm

Keywords: 6s194 added

comment:13 Changed 19 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 17 months ago by dgoulet

Sponsor: SponsorRSponsorR-can

Move those from SponsorR to SponsorR-can.

comment:15 Changed 9 months ago by teor

Milestone: Tor: 0.2.???Tor: 0.3.???

Milestone renamed

comment:16 Changed 8 months ago by nickm

Keywords: tor-03-unspecified-201612 added
Milestone: Tor: 0.3.???Tor: unspecified

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

comment:17 Changed 3 months ago by nickm

Keywords: tor-03-unspecified-201612 removed

Remove an old triaging keyword.

comment:18 Changed 3 months ago by nickm

Status: assignednew

Change the status of all assigned/accepted Tor tickets with owner="" to "new".

comment:19 Changed 3 months ago by dgoulet

Component: Core Tor/TorObfuscation/Obfsproxy
Owner: set to asn
Points: medium
Severity: Normal
Sponsor: SponsorR-can

comment:20 Changed 3 months ago by nickm

Keywords: maybe-bad-idea needs-discussion added

Other privacy-preserving collation mechanisms may wind up replacing this. I still think it's a fun idea.

Note: See TracTickets for help on using tickets.