aboutsummaryrefslogtreecommitdiff
path: root/spec/socks-extensions.md
diff options
context:
space:
mode:
Diffstat (limited to 'spec/socks-extensions.md')
-rw-r--r--spec/socks-extensions.md10
1 files changed, 5 insertions, 5 deletions
diff --git a/spec/socks-extensions.md b/spec/socks-extensions.md
index 6486215..d4d7010 100644
--- a/spec/socks-extensions.md
+++ b/spec/socks-extensions.md
@@ -22,8 +22,8 @@ to another address and port. The SOCKS server establishes the connection,
and reports success or failure to the client. After the connection has
been established, the client application uses the TCP stream as usual.
-Tor supports SOCKS4 as defined in [1], SOCKS4A as defined in [2], and
-SOCKS5 as defined in [3] and [4].
+Tor supports SOCKS4 as defined in \[1\], SOCKS4A as defined in \[2\], and
+SOCKS5 as defined in \[3\] and \[4\].
The stickiest issue for Tor in supporting clients, in practice, is forcing
DNS lookups to occur at the OR side: if clients do their own DNS lookup,
@@ -75,7 +75,7 @@ manpage.)
# Name lookup
As an extension to SOCKS4A and SOCKS5, Tor implements a new command value,
-"RESOLVE" [F0]. When Tor receives a "RESOLVE" SOCKS command, it initiates
+"RESOLVE" \[F0\]. When Tor receives a "RESOLVE" SOCKS command, it initiates
a remote lookup of the hostname provided as the target address in the SOCKS
request. The reply is either an error (if the address couldn't be
resolved) or a success response. In the case of success, the address is
@@ -84,7 +84,7 @@ stored in the portion of the SOCKS response reserved for remote IP address.
(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" [F1]. In response to a "RESOLVE_PTR" SOCKS5 command with
+"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.
@@ -94,7 +94,7 @@ address" portion of the reply.
# Other command extensions
-Tor 0.1.2.4-alpha added a new command value: "CONNECT_DIR" [F2].
+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