[tor-bugs] #6284 [Flashproxy]: make use of Chrome TCP sockets instead of websockets

[Tor Bug Tracker & Wiki]

#6284: make use of Chrome TCP sockets instead of websockets
-------------------------+--------------------------------------------------
 Reporter:  gsathya      |          Owner:  dcf
     Type:  enhancement  |         Status:  new
 Priority:  normal       |      Milestone:     
Component:  Flashproxy   |        Version:     
 Keywords:               |         Parent:     
   Points:               |   Actualpoints:     
-------------------------+--------------------------------------------------

Comment(by dcf):

 Replying to [ticket:6284 gsathya]:
 > Chrome has experimental TCP socket API -
 http://code.google.com/chrome/extensions/trunk/experimental.socket.html
 which is going to be merged soon-ish into stable -
 http://codereview.chromium.org/10440097/
 >
 > Do we want to use this?

 The above doc link is broken; here are some newer ones:
 * https://developer.chrome.com/apps/app_network.html
 * https://developer.chrome.com/apps/socket.html
 * https://github.com/GoogleChrome/chrome-app-samples/tree/master/udp

 I get the impression that this API is available only to Chrome "apps,"
 whatever those are. So it likely wouldn't be as easy as running the
 JavaScript flash proxy.

 But if someone is willing to install an "app," then we could connect to
 any Tor relay without a server transport plugin, and could play NAT
 piercing games with UDP.

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