diff options
| -rw-r--r-- | control-spec.txt | 2 | ||||
| -rw-r--r-- | socks-extensions.txt | 9 |
2 files changed, 6 insertions, 5 deletions
diff --git a/control-spec.txt b/control-spec.txt index a79973e..a675771 100644 --- a/control-spec.txt +++ b/control-spec.txt @@ -347,7 +347,7 @@ $Id$ set through any mechanism. "address" -- the best guess at our external IP address. If we - have no guess, return a 551 error. + have no guess, return a 551 error. (Added in 0.1.2.2-alpha) "circuit-status" A series of lines as for a circuit status event. Each line is of diff --git a/socks-extensions.txt b/socks-extensions.txt index 8040a8b..46cd983 100644 --- a/socks-extensions.txt +++ b/socks-extensions.txt @@ -47,10 +47,11 @@ Tor's extensions to the SOCKS protocol (We support RESOLVE in SOCKS4 too, even though it is unnecessary.) For SOCKS5 only, we support reverse resolution with a new command value, - "RESOLVE_PTR". In response to a "RESOLVE_PTR" SOCKS5 command with an IPv4 - address as its target, Tor attempts to find the canonical hostname for that - IPv4 record, and returns it in the "server bound address" portion of the - reply. (This was not supported before Tor 0.1.2.2-alpha) + "RESOLVE_PTR" [F1]. In response to a "RESOLVE_PTR" SOCKS5 command with + an IPv4 address as its target, Tor attempts to find the canonical + hostname for that IPv4 record, and returns it in the "server bound + address" portion of the reply. + (This command was not supported before Tor 0.1.2.2-alpha.) 3. HTTP-resistance |