commit 1656e00cabb9d638c705494bbd3cfe40244eaee6 Author: George Kadianakis desnacked@riseup.net Date: Mon Dec 24 20:32:51 2012 +0200
Pass name of transport to the Extended ORPort. --- proposals/196-transport-control-ports.txt | 12 +++++++++--- 1 file changed, 9 insertions(+), 3 deletions(-)
diff --git a/proposals/196-transport-control-ports.txt b/proposals/196-transport-control-ports.txt index 549e8ce..0488934 100644 --- a/proposals/196-transport-control-ports.txt +++ b/proposals/196-transport-control-ports.txt @@ -67,8 +67,11 @@ Target: 0.2.4.x bytes sent by the transport will be those tunneled over it. (body ignored)
- [0x0001] USERADDR: an address:port string that represents the user's - address. + [0x0001] USERADDR: an address:port string that represents the + user's address. + + [0x0002] TRANSPORT: a string of the name of the pluggable + transport currently in effect on the connection.
Replies sent from tor to the proxy are:
@@ -82,7 +85,10 @@ Target: 0.2.4.x the TransportControlPort. See the 'Association and identifier creation' section below.
- Parties should ignore command codes that they do not understand. + Parties MUST ignore command codes that they do not understand. + + If the server receives a recognized command that does not parse, it + MUST close the connection to the client.
3.2. The new TransportControlPort protocol