diff options
author | Wladimir J. van der Laan <laanwj@gmail.com> | 2016-10-25 07:36:07 +0200 |
---|---|---|
committer | Wladimir J. van der Laan <laanwj@gmail.com> | 2016-10-25 07:37:30 +0200 |
commit | 67728a389ccf128fc25262668b2a23f8ef73e1d6 (patch) | |
tree | f4f4bb7fda28ee9677b91c6c79e9ba5a636fe4c3 | |
parent | ced22d035ac0f769c9c7cc21ad24d2caafb4b4e9 (diff) | |
parent | 3421e746017079b119a661108334d58e4bfde34b (diff) |
Merge #9004: Clarify `listenonion`
3421e74 Clarify `listenonion` (unsystemizer)
-rw-r--r-- | doc/tor.md | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/tor.md b/doc/tor.md index 2f376af4c7..a05979fca8 100644 --- a/doc/tor.md +++ b/doc/tor.md @@ -99,10 +99,10 @@ This means that if Tor is running (and proper authentication has been configured Bitcoin Core automatically creates a hidden service to listen on. This will positively affect the number of available .onion nodes. -This new feature is enabled by default if Bitcoin Core is listening, and -a connection to Tor can be made. It can be configured with the `-listenonion`, -`-torcontrol` and `-torpassword` settings. To show verbose debugging -information, pass `-debug=tor`. +This new feature is enabled by default if Bitcoin Core is listening (`-listen`), and +requires a Tor connection to work. It can be explicitly disabled with `-listenonion=0` +and, if not disabled, configured using the `-torcontrol` and `-torpassword` settings. +To show verbose debugging information, pass `-debug=tor`. Connecting to Tor's control socket API requires one of two authentication methods to be configured. For cookie authentication the user running bitcoind must have write access |