[tor-bugs] #5418 [BridgeDB]: Review and deploy code so that BridgeDB can give out unblocked bridges
Tor Bug Tracker & Wiki
blackhole at torproject.org
Wed Apr 1 01:18:25 UTC 2015
#5418: Review and deploy code so that BridgeDB can give out unblocked bridges
-------------------------+-------------------------------------------------
Reporter: runa | Owner: isis
Type: task | Status: closed
Priority: normal | Milestone:
Component: | Version:
BridgeDB | Keywords: bridgedb-database, reachability,
Resolution: fixed | bridgedb-0.3.2
Actual Points: | Parent ID:
Points: |
-------------------------+-------------------------------------------------
Changes (by isis):
* status: needs_revision => closed
* keywords: bridgedb-database,reachability,difficult => bridgedb-database,
reachability, bridgedb-0.3.2
* resolution: => fixed
Comment:
I've rewritten large sections of the code for setting a bridge as being
blocked, or its transports, or some of its transports, or some ports, or
some addresses, and any combination of any of that. This code is in the
new `bridgedb.bridges.Bridge`
[https://gitweb.torproject.org/user/isis/bridgedb.git/tree/lib/bridgedb/bridges.py?h=develop#n777
class] that was introduced for #9380.
I've decided for #12505 to remove all the remnant code from #5027. It
needed to be entirely refactored. The database table which was set up for
the code hasn't ever been used, so I'm ripping the whole thing out.
The last pieces that we'll need are:
* (#12031) A way to store info for blocked bridges in the new databases.
This should be quite simple given the new data structures and the methods
exposed by the new `bridgedb.bridges.Bridge` class.
* (#12547) We'll need parsers for the `bridge_reachability`
[http://pipeline.infra.ooni.nu/CN/ reports created by OONI].
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/5418#comment:3>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
More information about the tor-bugs
mailing list