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

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

#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     |         Parent:     
   Points:                       |   Actualpoints:     
---------------------------------+------------------------------------------

Comment(by asn):

 After discussions in the dev meeting, consensus is:

 a) First, investigate the option of simply using the code of obfs2 in
 flashproxy. This involves librarifying obfs2 in some way, and/or
 implementing flashproxy within the pyobfsproxy framework. This should be
 the easiest way of doing this ticket.

 b) Then, investigate SOCKS proxy chaining like it was initially suggested
 in this ticket. This involves implementing #8402, specing out a way to do
 the chaining (Tor should pass the chain to the PT proxy somehow), specing
 out a way to collect statistics on chained transports, and implementing
 the whole thing. This is more painful. There are also other problems, like
 distinguishing possible transport combinations from impossible ones (e.g.
 obfs2|websocket (doable and useful) from websocket|obfs2 (doesn't make
 much sense))

 c) Finally, we should start researching a multilayer pluggable transport
 theory, in the same way that regular network protocols are implemented.
 This means that content-shaping should be on the bottom (obfs2, obfs3,
 packet-length shapers, etc.), appearance-shaping should be above (like an
 HTTP transport, a base64 transport, etc.) and a transport layer should be
 on top (like flashproxy, skypemorph, webrtc, regular socket, etc.). This
 is more research-y, but if done correctly it might allow greater reuse of
 transports, and will cause an explosion on the number of pluggable
 transports we have.

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