aboutsummaryrefslogtreecommitdiff
path: root/doc/tor.md
diff options
context:
space:
mode:
authorMarcoFalke <falke.marco@gmail.com>2015-09-06 17:54:41 +0200
committerMarcoFalke <falke.marco@gmail.com>2015-09-06 18:17:35 +0200
commit238851bf645709c8a333f48517ffcdb29a9c1434 (patch)
tree23faaaf3583a7e7db64e584638372c99a300d941 /doc/tor.md
parent536207f3167daad1fa3d60a1de7d9cb55db28ac9 (diff)
[doc] [tor] Clarify when to use bind
c.f. #6585
Diffstat (limited to 'doc/tor.md')
-rw-r--r--doc/tor.md11
1 files changed, 8 insertions, 3 deletions
diff --git a/doc/tor.md b/doc/tor.md
index 560f71fa27..f8b94d19d1 100644
--- a/doc/tor.md
+++ b/doc/tor.md
@@ -70,9 +70,14 @@ In a typical situation, where you're only reachable via Tor, this should suffice
./bitcoind -proxy=127.0.0.1:9050 -externalip=57qr3yd1nyntf5k.onion -listen
-(obviously, replace the Onion address with your own). If you don't care too much
-about hiding your node, and want to be reachable on IPv4 as well, additionally
-specify:
+(obviously, replace the Onion address with your own). It should be noted that you still
+listen on all devices and another node could establish a clearnet connection, when knowing
+your address. To mitigate this, additionally bind the address of your Tor proxy:
+
+ ./bitcoind ... -bind=127.0.0.1
+
+If you don't care too much about hiding your node, and want to be reachable on IPv4
+as well, use `discover` instead:
./bitcoind ... -discover