[tor-bugs] #9164 [Flashproxy]: Is Flashproxy pluggable transport really working? Tests, comments and questions

[Tor Bug Tracker & Wiki]

#9164: Is Flashproxy pluggable transport really working? Tests, comments and
questions
------------------------+---------------------------------------------------
 Reporter:  Aymeric     |          Owner:  dcf
     Type:  defect      |         Status:  new
 Priority:  normal      |      Milestone:     
Component:  Flashproxy  |        Version:     
 Keywords:              |         Parent:     
   Points:              |   Actualpoints:     
------------------------+---------------------------------------------------

Comment(by arlolra):

 Replying to [ticket:9164 Aymeric]:

 > So I modified a little bit flashproxy.js, see
 http://www.ianonym.com/test.html, mainly I modified the polling timer to
 the facilitator to 10s and activated the debug.

 This wasn't necessary. The embed code can accept querystring parameters,
 {{{
 embed.html?facilitator_poll_interval=10&initial_facilitator_poll_interval=10&debug=1
 }}}

 > Probably it's related to #9008 but for most of the routers returned by
 the facilitator the websocket connexion failed, see file herattached.

 Seems like #9008. There's at least one successful connection in the
 attached,
 https://trac.torproject.org/projects/tor/attachment/ticket/9164/tor_ff2.html#L1180

 > During a period of time it worked only two times, and what is strange is
 that it failed afterwards with the "successful" routers.
 >
 > And a direct websocket connexion attempt toward these "successfull"
 routers failed too.

 This sounds confused. I'm not sure what you mean by ''router'' here.

 Take for example,
 {{{
 Facilitator: got client:{ host: "xxx.xxx.xxx.xxx", port: 9000 } relay:{
 host: "173.255.221.44", port: 9901 }.
 }}}

 In this scenario, '''you''' are the flashproxy. You've polled the
 facilitator and received a client IP. You then make two websocket
 connections, one to the client on port 9000 and one to the relay on port
 9901. When the connections establish, your only job is to shuttle bits
 between those two ports. On each end, tor is running using the websocket
 (not flashproxy) pluggable transport.

 The idea being that the flashproxies are ephemeral but in constant supply.
 The websocket PT exists independently of flashproxies and can be used for
 direct connections.

 I would suggest taking a look at the diagram here,
 https://crypto.stanford.edu/flashproxy/#how-it-works

 Forgive me if you already understand all this and I'm misinterpreting your
 question.

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