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

Re: [tor-bugs] #9349 [Flashproxy]: flashproxy facilitator: Allow clients to specify transports

#9349: flashproxy facilitator: Allow clients to specify transports
----------------------------+-------------------
     Reporter:  asn         |      Owner:  dcf
         Type:  task        |     Status:  new
     Priority:  normal      |  Milestone:
    Component:  Flashproxy  |    Version:
   Resolution:              |   Keywords:
Actual Points:              |  Parent ID:  #7167
       Points:              |
----------------------------+-------------------

Comment (by infinity0):

 OK, I think I get the "outermost transport" thing now - a proxy running in
 a browser has to make use of something like websocket in other to talk to
 the client/server in the first place; OTOH a standalone proxy running on
 e.g. node.js can open raw sockets, like in arlolra's commit.

 So each proxy has a suffix-constraint that matches against the full
 transport chain. And if I understood correctly, a raw TCP-TCP proxy can
 proxy anything *including* a obfs|websocket stream, assuming that it's
 valid to cut out the middle man in our websocket transport.

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