Ticket #9349: 0001-Add-pluggable-transport-client-registration-specific.patch

File 0001-Add-pluggable-transport-client-registration-specific.patch, 1.7 KB (added by asn, 6 years ago)
  • doc/design.txt

    From 92d1ee1980bca074cb176b68dc248cf0af6811be Mon Sep 17 00:00:00 2001
    From: George Kadianakis <desnacked@riseup.net>
    Date: Thu, 8 Aug 2013 16:12:32 +0300
    Subject: [PATCH] Add pluggable transport client registration specification.
    
    ---
     doc/design.txt |   18 +++++++++++++-----
     1 file changed, 13 insertions(+), 5 deletions(-)
    
    diff --git a/doc/design.txt b/doc/design.txt
    index 7f1e548..51da9cf 100644
    a b Design of flash proxies 
    100100  flash proxy and the local Tor client.
    101101
    102102  On startup, the client transport plugin sends a registration message
    103   to the facilitator, informing the facilitator that it is waiting for a
    104   connection. The facilitator will later hand this registration to a
    105   flash proxy. The registration message is an HTTP POST request of the
    106   form:
     103  to the facilitator, informing the facilitator that it is waiting for
     104  a connection. If the client transport plugin obfuscates its
     105  connections using pluggable transports, then it also appends the
     106  listening address of its transports to the registration message.
     107
     108  The facilitator will later hand this registration to a flash
     109  proxy. The registration message is an HTTP POST request of the form:
    107110
    108111    POST / HTTP/1.0
    109112
    110     client=[<address>]:<port>
     113    client=[<address>]:<port>[&client-<transport>=[<address>]:<port>]
     114
     115  For example a registration message would look like this:
     116    client=1.2.3.4:9000
     117  or like this (with pluggable transport support):
     118    client=1.2.3.4:9000&client-obfs3=1.2.3.4:10000
    111119
    112120  The facilitator sends a 200 reply if the registration was successful
    113121  and an error status otherwise. If the transport plugin omits the