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

["Tor Bug Tracker & Wiki" <blackhole@xxxxxxxxxxxxxx>]

#5578: Investigate WebRTC for flash proxy NAT punching
----------------------------+-----------------
     Reporter:  dcf         |      Owner:  dcf
         Type:  task        |     Status:  new
     Priority:  normal      |  Milestone:
    Component:  Flashproxy  |    Version:
   Resolution:              |   Keywords:
Actual Points:              |  Parent ID:
       Points:              |
----------------------------+-----------------

Comment (by infinity0):

 Taking a step back, perhaps bundling the SDP offer with the client
 registration is not the best approach. There are a few reasons:

 - the SDP offer is supposed to be fresh for each connection (with a new
 ice-ufrag and ice-pwd), though it does contains information that is
 constant across connections (such as ICE candidates). By contrast,
 flashproxy-client does not currently try to send a new registration for
 every single connection it wants. We would also have to tweak the client-
 side webrtc code to give out constant ice-ufrag/ice-pwd which is against
 the RFC (link above) and might open up attacks.

 - there is no "listen" port, nor any other way of receiving information,
 so we don't know (beyond the first connection) when subsequent proxies
 will want to contact us.

 So maybe a separate signalling mechanism would be best.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/5578#comment:31>
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