From aa2ba740ffae7f81582c5771b80253c3668f03f2 Mon Sep 17 00:00:00 2001 From: Nick Mathewson Date: Fri, 22 Sep 2006 00:43:55 +0000 Subject: r8894@Kushana: nickm | 2006-09-21 18:30:42 -0400 Specify and implement SOCKS5 interface for reverse hostname lookup. svn:r8451 --- socks-extensions.txt | 6 ++++++ 1 file changed, 6 insertions(+) (limited to 'socks-extensions.txt') 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 -- cgit v1.2.3-54-g00ecf