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

[Tor Bug Tracker & Wiki]

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

Comment (by infinity0):

 Replying to [comment:16 dcf]:
 > `options.relays` should be indexed not by complete transport chains, but
 by transport chains excluding their last element. It should be possible
 for an obfs3|websocket client to talk to an obfs3|tcp relay, if there is a
 proxy that speaks both websocket and tcp. To be specific you should key by
 the tuple `("obfs3",)` and not `("obfs3", "websocket")`.
 >
 As I understand it, this would additionally require additional changes on
 the client side to parse the response from the facilitator and initiate
 connections via the correct engines (when we finally do support more than
 2 types of relay e.g. out of websocket/webrtc/plain-tcp). At the moment
 the client only sends "transport=websocket", it doesn't parse the response
 and assumes websocket-websocket proxying.

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