diff options
| -rw-r--r-- | socks-extensions.txt | 10 | ||||
| -rw-r--r-- | tor-spec.txt | 3 |
2 files changed, 12 insertions, 1 deletions
diff --git a/socks-extensions.txt b/socks-extensions.txt index 46cd983..8097c66 100644 --- a/socks-extensions.txt +++ b/socks-extensions.txt @@ -53,7 +53,15 @@ Tor's extensions to the SOCKS protocol address" portion of the reply. (This command was not supported before Tor 0.1.2.2-alpha.) -3. HTTP-resistance +3. Other command extensions. + + Tor 0.1.2.4-alpha added a new command value: "CONNECT_DIR" [F2]. + In this case, Tor will open an encrypted direct TCP connection to the + directory port of the Tor server specified by address:port (the port + specified should be the ORPort of the server). It uses a one-hop tunnel + and a "BEGIN_DIR" relay cell to accomplish this secure connection. + +4. HTTP-resistance Tor checks the first byte of each SOCKS request to see whether it looks more like an HTTP request (that is, it starts with a "G", "H", or "P"). If diff --git a/tor-spec.txt b/tor-spec.txt index 1f18f19..ca82e1c 100644 --- a/tor-spec.txt +++ b/tor-spec.txt @@ -733,6 +733,9 @@ TODO: If the Tor server is not running a directory service, it should respond with a REASON_NOTDIRECTORY RELAY_END cell. + Clients MUST generate an all-zero payload for RELAY_BEGIN_DIR cells, + and servers MUST ignore the payload. + [RELAY_BEGIN_DIR was not supported before Tor 0.1.2.2-alpha; clients SHOULD NOT send it to routers running earlier versions of Tor.] |