[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:  needs_review
 Priority:  normal                       |      Milestone:              
Component:  Pluggable transport          |        Version:              
 Keywords:  SponsorF20131101 flashproxy  |         Parent:              
   Points:                               |   Actualpoints:              
-----------------------------------------+----------------------------------

Comment(by asn):

 Replying to [comment:17 dcf]:
 > One thing we didn't think about was the flash proxy facilitator. The
 reason you have to run your own flash proxy in the instructions above is
 that the facilitator doesn't know that it needs to give a obfs3-in-
 websocket relay to proxies that are serving certain clients. Obviously
 connecting to the plain websocket relay that the facilitator uses now,
 won't work. We need to think of a way to allow a client to say that it
 wants to connect to a different kind of relay. Like client registration
 messages, which currently only contain the client IP and port, could also
 contain the nested protocols the client wants to use. The facilitator
 would check to see if it knows of any relays having that nesting, and
 reply to proxies with an appropriate relay. I have some previous thinking
 along these lines in comment:2:ticket:5578, comment:5:ticket:7944.
 >

 Opened #9349 for this task.

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