[tor-bugs] #9349 [Flashproxy]: flashproxy facilitator: Allow clients to specify transports

Tor Bug Tracker & Wiki blackhole at torproject.org
Wed Jul 31 15:57:58 UTC 2013

#9349: flashproxy facilitator: Allow clients to specify transports
 Reporter:  asn         |          Owner:  dcf  
     Type:  task        |         Status:  new  
 Priority:  normal      |      Milestone:       
Component:  Flashproxy  |        Version:       
 Keywords:              |         Parent:  #7167
   Points:              |   Actualpoints:       

Comment(by asn):

 Items that need to be done to achieve the goal of this ticket:

 - Implement advanced client registrations, where clients can also specify
 a transport when they ask for a flashproxy. David in comment:2:ticket:5578
 said that registrations currently look like this:
 and they could be changed to look similar to this:

 - Facilitators should be able to have multiple bridges that they can
 suggest to flashproxies. The facilitator currently reads a single bridge
 using the `--address` CLI switch
 We will need to pass multiple bridges in the future, so we might want to
 use a config file, where we put our bridges and annotate them with the
 transports they support. Possible example of such a config file:

 - The facilitator should parse the new client-registration, match it up
 with a registered bridge, and return the bridge as part of its response.
 We might also want to make a response for "transport name not known".

 All of the tasks above should be spec'ed.
 Doesn't look too hard!

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

More information about the tor-bugs mailing list