[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #5684 [Metrics Data Processor]: Should we stop sanitizing nicknames in bridge descriptors?

#5684: Should we stop sanitizing nicknames in bridge descriptors?
------------------------------------+---------------------------------------
 Reporter:  karsten                 |          Owner:     
     Type:  enhancement             |         Status:  new
 Priority:  normal                  |      Milestone:     
Component:  Metrics Data Processor  |        Version:     
 Keywords:                          |         Parent:     
   Points:                          |   Actualpoints:     
------------------------------------+---------------------------------------
Changes (by aagbsn):

 * cc: aagbsn (added)


Comment:

 Some options:

 1. Do not sanitize the nicknames
   - counting Tor Cloud bridges would be easy
   - might reveal bridges whose nicknames correlate with public relays
   - reveals approximate network location (AWS)

 More than half of all bridges have a unique nickname. How do we estimate
 the risk of not sanitizing nicknames?

 2. Mention Tor Cloud in the extra-info 'platform' string
   - counting Tor Cloud bridges would be easy
   - could indicate approximate network location (AWS)
   - Tor Cloud image would need to be updated and re-deployed

 Is this possible? How does Tor decide what to put in the platform string?

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/5684#comment:1>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs