[tor-bugs] #7167 [Pluggable transport]: Combine traffic obfuscation with address diversity of flash proxy

[Tor Bug Tracker & Wiki]

#7167: Combine traffic obfuscation with address diversity of flash proxy
-----------------------------------------+----------------------------------
 Reporter:  karsten                      |          Owner:  asn
     Type:  project                      |         Status:  new
 Priority:  normal                       |      Milestone:     
Component:  Pluggable transport          |        Version:     
 Keywords:  SponsorF20131101 flashproxy  |         Parent:     
   Points:                               |   Actualpoints:     
-----------------------------------------+----------------------------------

Comment(by nickm):

 Some notes on comment:8 above, at asn's request.

 I agree that (a) seems best of the listed. But it measns that every proxy
 must accept an extended orport form of itself, which is a bit annoying.
 It's not so differrent from (b), which also requires that every proxy
 support a new protocol: the only difference here is that the protocol is
 one we already designed.

 (c) is probably easiest, but needs a bunch of ports if the clients are
 slow to connect.  Also, wouldn't you need to make the client use separate
 target ports for each incoming connection, to tell them apart?  I don't
 believe there's a way to do that with the current protocol without
 launching a bunch of clients.

 (b) seems like it might be a good idea, but it will be the hardest.  It
 might be something to think about in the future, but if you're going to do
 it, do it in some way that avoids using sockets needlessly -- maybe by
 allowing the plugins to do this kind of communication over a preconfigured
 pipe, or an in-memory API, or something.  But that's harder, and could
 wait IMO.

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