aboutsummaryrefslogtreecommitdiff
path: root/doc/tor.md
diff options
context:
space:
mode:
authorWladimir J. van der Laan <laanwj@gmail.com>2014-07-24 15:55:49 +0200
committerWladimir J. van der Laan <laanwj@gmail.com>2014-07-24 15:57:24 +0200
commit59abcefc2eec7ede6f098dbcf7323aef6e746a4a (patch)
tree27d458468c40494bc5505a8366b7e144dd26b446 /doc/tor.md
parent7bf8ab9dd3efb7ebc685e4ac02b05e6d5eba107d (diff)
downloadbitcoin-59abcefc2eec7ede6f098dbcf7323aef6e746a4a.tar.xz
doc: remove any mention of SOCKS4
SOCKS4 support was removed in 0127a9b, as well as the `-socks=` option.
Diffstat (limited to 'doc/tor.md')
-rw-r--r--doc/tor.md5
1 files changed, 0 insertions, 5 deletions
diff --git a/doc/tor.md b/doc/tor.md
index b5eb91e12e..560f71fa27 100644
--- a/doc/tor.md
+++ b/doc/tor.md
@@ -13,11 +13,6 @@ configure Tor.
The first step is running Bitcoin behind a Tor proxy. This will already make all
outgoing connections be anonymized, but more is possible.
- -socks=5 SOCKS5 supports connecting-to-hostname, which can be used instead
- of doing a (leaking) local DNS lookup. SOCKS5 is the default,
- but SOCKS4 does not support this. (SOCKS4a does, but isn't
- implemented).
-
-proxy=ip:port Set the proxy server. If SOCKS5 is selected (default), this proxy
server will be used to try to reach .onion addresses as well.