[tor-bugs] #6513 [BridgeDB]: Set up separate bridge email autoresponder for BBG

[Tor Bug Tracker & Wiki]

#6513: Set up separate bridge email autoresponder for BBG
----------------------+-----------------------------------------------------
 Reporter:  arma      |          Owner:     
     Type:  project   |         Status:  new
 Priority:  normal    |      Milestone:     
Component:  BridgeDB  |        Version:     
 Keywords:  SponsorJ  |         Parent:     
   Points:            |   Actualpoints:     
----------------------+-----------------------------------------------------

Comment(by arma):

 Replying to [comment:4 aagbsn]:
 > Do you mean: write a script to respond to an email with the same 3
 bridges, and figure out what to do when those 3 get blocked, or

 This is the one I meant. On the theory that a) setting it up this way is
 quite easy to do, and b) if the system gets attacked by an enumerating
 adversary, they'll likely get all the bridges we give out, so let's keep
 most of them in reserve for now.

 Though that said, I wonder if we want to require that the mails come from
 gmail (to check dkim), or be more flexible (and risk letting a jerk cause
 us to spam people). I'll check with Kelly.

 > > It would be great to have this set up by mid August. Aaron, are you a
 good person to pop one of these up next to / part of bridgedb?
 >
 > It should be pretty easy to set up a BridgeDB instance that:
 >
 > a) disabled https distributor, enabled email distributor
 > b) reads the list of bridges from a static set of descriptors in a file.

 Sounds good. Now that you phrase it like that, we could imagine setting up
 a separate Bridge Directory Authority, and having it do the reachability
 tests, generate networkstatus documents, and rsync them to this bridgedb
 just like the main one. But let's not worry about that yet.

 That said, it sounds like you'd need to hack bridgedb to just read
 descriptors directly, rather than wanting a networkstatus document first.

 I'll mail you a pair of bridges offline, and then we should get this up
 and going rsn.

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