aboutsummaryrefslogtreecommitdiff
path: root/socks-extensions.txt
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2006-09-22 00:43:55 +0000
committerNick Mathewson <nickm@torproject.org>2006-09-22 00:43:55 +0000
commitaa2ba740ffae7f81582c5771b80253c3668f03f2 (patch)
treec5154a12d3312bab0e292a247bfbcd31ff4301af /socks-extensions.txt
parentfddab1eb913763577d40c52f18ba0864cf02532c (diff)
downloadtorspec-aa2ba740ffae7f81582c5771b80253c3668f03f2.tar.gz
torspec-aa2ba740ffae7f81582c5771b80253c3668f03f2.zip
r8894@Kushana: nickm | 2006-09-21 18:30:42 -0400
Specify and implement SOCKS5 interface for reverse hostname lookup. svn:r8451
Diffstat (limited to 'socks-extensions.txt')
-rw-r--r--socks-extensions.txt6
1 files changed, 6 insertions, 0 deletions
diff --git a/socks-extensions.txt b/socks-extensions.txt
index 7022af1..8040a8b 100644
--- a/socks-extensions.txt
+++ b/socks-extensions.txt
@@ -46,6 +46,12 @@ 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)
+
3. HTTP-resistance
Tor checks the first byte of each SOCKS request to see whether it looks