[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

[tor-bugs] #5578 [Flashproxy]: Investigate WebRTC for flash proxy NAT punching



#5578: Investigate WebRTC for flash proxy NAT punching
------------------------+---------------------------------------------------
 Reporter:  dcf         |          Owner:  dcf
     Type:  task        |         Status:  new
 Priority:  minor       |      Milestone:     
Component:  Flashproxy  |        Version:     
 Keywords:              |         Parent:     
   Points:              |   Actualpoints:     
------------------------+---------------------------------------------------
 hellais suggested WebRTC (http://www.webrtc.org/,
 https://en.wikipedia.org/wiki/WebRTC) as a way to directly connect
 browsers behind NATs. This could be useful for the JavaScript flash proxy,
 which otherwise doesn't work at all when the censored user is behind NAT.

 We should examine WebRTC to find out at least
 # How much information it discloses to a third party. (For facilitation of
 NAT punching, for example. This was a problem with the Adobe RTMFP
 transport in the Flash-based proxy.)
 # How common it is or can be expected to become; i.e., will a censor be
 reluctant to block it wholesale.
 # What are the implications for protocol fingerprinting.
 # What browsers it is supported in.
 # How easy it is to implement and deploy.

 * WebRTC API http://dev.w3.org/2011/webrtc/editor/webrtc.html
 * Architecture http://www.webrtc.org/reference/architecture note
 references to STUN and ICE.

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/5578>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs