aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorWladimir J. van der Laan <laanwj@gmail.com>2015-09-08 15:46:09 +0200
committerWladimir J. van der Laan <laanwj@gmail.com>2015-09-08 15:50:02 +0200
commite8bb8ad85abe3d00b9dcc9f8cdbb0512b4ae46bb (patch)
tree5e1f04f1e8bf4202e5818678686236ff7177eab9
parentcd381d771953805a0784e17e9fa7e9c0d2524f55 (diff)
parent238851bf645709c8a333f48517ffcdb29a9c1434 (diff)
Merge pull request #6643
238851b [doc] [tor] Clarify when to use bind (MarcoFalke)
-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