Changes between Version 1 and Version 2 of Ticket #9349, comment 23


Ignore:
Timestamp:
Sep 19, 2013, 3:31:20 PM (6 years ago)
Author:
infinity0
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #9349, comment 23

    v1 v2  
    11OK, 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. 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.
    22
    3 So what really matters, is not the "outermost layer", but a "suffix constraint" for each proxy, and could be empty for a raw TCP-TCP proxy, which must be matched against the full transport chain.
     3So what really matters, is not the "outermost layer", but a "suffix constraint" for each proxy, which must be matched against the full transport chain. In the case of a raw TCP-TCP proxy, this suffix constraint is empty, and therefore matches all transport chains.