[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 asn):

 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")`.
 >

 Hm, would this functionality work currently?

 To have an obfs3|websocket client talk to an obfs3|tcp relay, doesn't the
 flashproxy have to first strip off the websocket frame? Does this happen
 currently? It was my impression that there is a bridge-side websocket
 transport that strips off the websocket frames.

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