aboutsummaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorWladimir J. van der Laan <laanwj@gmail.com>2016-09-27 15:03:12 +0200
committerWladimir J. van der Laan <laanwj@gmail.com>2016-09-27 15:04:40 +0200
commitac01ff22bed73993261983b355c7cb3e2f3cb7cf (patch)
treecc9b3db6b1b3afc226b557158465a373d63fc21c /doc
parent920ca1f0bf0b786250e3119a05984e0c2af1350a (diff)
doc: Add privacy recommendation when running hidden service
Diffstat (limited to 'doc')
-rw-r--r--doc/tor.md11
1 files changed, 10 insertions, 1 deletions
diff --git a/doc/tor.md b/doc/tor.md
index 79f1563021..2f376af4c7 100644
--- a/doc/tor.md
+++ b/doc/tor.md
@@ -113,4 +113,13 @@ the user running bitcoind to the same group and setting permissions appropriatel
Debian-based systems the user running bitcoind can be added to the debian-tor group,
which has the appropriate permissions. An alternative authentication method is the use
of the `-torpassword` flag and a `hash-password` which can be enabled and specified in
-Tor configuration. \ No newline at end of file
+Tor configuration.
+
+4. Privacy recommendations
+---------------------------
+
+- Do not add anything but bitcoin ports to the hidden service created in section 2.
+ If you run a web service too, create a new hidden service for that.
+ Otherwise it is trivial to link them, which may reduce privacy. Hidden
+ services created automatically (as in section 3) always have only one port
+ open.