[tor-bugs] #5418 [BridgeDB]: Review and deploy code so that BridgeDB can give out unblocked bridges

[Tor Bug Tracker & Wiki]

#5418: Review and deploy code so that BridgeDB can give out unblocked bridges
-------------------------+-------------------------------------------------
     Reporter:  runa     |      Owner:  isis
         Type:  task     |     Status:  assigned
     Priority:  normal   |  Milestone:
    Component:           |    Version:
  BridgeDB               |   Keywords:  bridgedb-
   Resolution:           |  database,reachability,difficult
Actual Points:           |  Parent ID:
       Points:           |
-------------------------+-------------------------------------------------
Changes (by isis):

 * owner:  aagbsn => isis
 * keywords:   => bridgedb-database,reachability,difficult
 * status:  new => assigned
 * cc: isis (added)


Comment:

 This code will need some love. In particular, we will likely want a new
 database which stores:

   1. The ip:port pair which is "blocked"
   2. What country the block is seen in.
   3. When the block was first discovered/reported in that country.
   4. The method used to discover the blocking
   5. The method used to verify the block, or additional confirmations (if
 using some sort of remote reporting mechanism).
   6. When the latest block verification/confirmation took place.

 This will therefore need to be on an "ip:port + country" basis. And,
 because this requires another database (or additional tables in the
 current one; but I'd prefer them to be kept separate), the code in
 `bridgedb.Bridges` which aagbsn wrote will need some love. Also, if I
 recall correctly, there were some old-style Python classes in there which
 will trigger some rather severe and annoying Python 2.x bugs.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/5418#comment:1>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online