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

Re: [tor-bugs] #2678 [BridgeDB]: bridgedb /16 filtering needs review

#2678: bridgedb /16 filtering needs review
-----------------------------+--------------------
     Reporter:  karsten      |      Owner:
         Type:  enhancement  |     Status:  closed
     Priority:  normal       |  Milestone:
    Component:  BridgeDB     |    Version:
   Resolution:  wontfix      |   Keywords:
Actual Points:               |  Parent ID:
       Points:               |
-----------------------------+--------------------
Changes (by isis):

 * status:  new => closed
 * resolution:   => wontfix


Comment:

 Replying to [comment:8 sysrqb]:
 > hrm, ok. I know there's a comment in the bridge selection code that says
 it does this, but it seems like it's misplaced. But I do think I remember
 seeing a check for this somewhere else, though. I have a feeling, in any
 case, we're going to want to come back to this as we get further into
 #7520.

 That comment is
 [https://gitweb.torproject.org/bridgedb.git/blob/HEAD:/lib/bridgedb/Bridges.py#l1042
 on this line], FWIW.

 And yes, the comment is misplaced. The line directly underneath it just
 takes all the bridges in the splitter. I'm not sure if implementing this
 is still a good idea, given that we have volunteer bridge operators
 running bridges very close to each other, esp. for PTs, and implementing
 this would likely severely decrease the bridges available to a user.

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