aboutsummaryrefslogtreecommitdiff
path: root/doc/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
commit213658f117f88eaeb21ffd61451155f451f67604 (patch)
tree31f4c5d408f6372cc08d1be2731f4c2ab10eced9 /doc/socks-extensions.txt
parent9bc8d69dfc4ddda5a9c8478b1f1e04490845ded0 (diff)
downloadtor-213658f117f88eaeb21ffd61451155f451f67604.tar
tor-213658f117f88eaeb21ffd61451155f451f67604.tar.gz
r8894@Kushana: nickm | 2006-09-21 18:30:42 -0400
Specify and implement SOCKS5 interface for reverse hostname lookup. svn:r8451
Diffstat (limited to 'doc/socks-extensions.txt')
-rw-r--r--doc/socks-extensions.txt6
1 files changed, 6 insertions, 0 deletions
diff --git a/doc/socks-extensions.txt b/doc/socks-extensions.txt
index 7022af14f..8040a8b03 100644
--- a/doc/socks-extensions.txt
+++ b/doc/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