diff options
| author | unsystemizer <unsystemizer@users.noreply.github.com> | 2016-10-24 15:49:46 +0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2016-10-24 15:49:46 +0800 |
| commit | 3421e746017079b119a661108334d58e4bfde34b (patch) | |
| tree | 7bdcc9ae176ec83d7eb5ab0c54cc7f3e1ce5575d /doc/tor.md | |
| parent | fd29348dbe82abb3a315d6226332c7470c2c88f2 (diff) | |
Clarify `listenonion`
> 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.
But it is correct to say that the feature is enabled *regardless* of whether a connection to Tor can be made.
I propose to clarify that so that users can eliminate these in their logs (when `listen=1` and no Tor).
And I think it's okay to clarify about the `listen` option, because on several occasions when I read this before I always assumed `listening` meant `server=1` which cost me a lot of time in troubleshooting.
```
2016-10-24 06:19:22.551029 tor: Error connecting to Tor control socket
2016-10-24 06:19:22.551700 tor: Not connected to Tor control port 127.0.0.1:9051, trying to reconnect
```
### What version of bitcoin-core are you using?
0.12.1
Diffstat (limited to 'doc/tor.md')
| -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 |