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

Re: [tor-bugs] #4771 [BridgeDB]: bridgedb should make clearer in its logs which addresses it knows are from bulk-exitlist



#4771: bridgedb should make clearer in its logs which addresses it knows are from
bulk-exitlist
--------------------------+--------------------------------------------
     Reporter:  arma      |      Owner:  isis
         Type:  defect    |     Status:  needs_review
     Priority:  minor     |  Milestone:
    Component:  BridgeDB  |    Version:
   Resolution:            |   Keywords:  isis2015Q1Q2, isisExB, isisExC
Actual Points:            |  Parent ID:
       Points:            |
--------------------------+--------------------------------------------
Changes (by isis):

 * status:  needs_information => needs_review


Comment:

 Replying to an email from Robert Ransom:
 > Replying to [comment:15 isis]:
 > > This fixes the issue with confusing logging, and also fixes the issue
 that changing your Tor exit gets you different bridges.
 >
 > That was intentional, and (at least back in 2011) arma/Roger considered
 it a good feature.
 >
 > At least it should spread out the load due to honest users who obtain
 bridges by HTTPS-over-Tor better than serving the same small set to all
 HTTPS-over-Tor bridge users.

 Ah, that is a good point!  But it also means that the whole subhashring
 for Tor users can be super easily scraped, meaning that if a user in China
 has already gotten their Tor working, and then they ask for bridges over
 Tor, they'll likely get bridges that are already blocked. :(

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/4771#comment:16>
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