[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:  assigned
     Priority:  minor     |  Milestone:
    Component:  BridgeDB  |    Version:
   Resolution:            |   Keywords:  isis2015Q1Q2, isisExB, isisExC
Actual Points:            |  Parent ID:
       Points:            |
--------------------------+--------------------------------------------

Comment (by isis):

 Replying to [comment:5 arma]:
 > Sounds reasonable. That said, does whatever we replaced it with (the
 thing that lets atlas tell you how your bridge is being distributed) know
 about this ipv5 hashring too?

 Onionoo no longer contains ``'pool_assignment'`` fields in its bridge
 details.json documents, and #13921 is the ticket for changing both Atlas
 and Globe to no longer have "Pool assignment" fields in the UIs. In
 Globe's case, it now has a "Transports" field instead which lists the PT
 methodnames supported by that bridge (or rather, it will, as soon as
 someone redeploys Globe).

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