diff options
| author | Jordan Baczuk <Jordan.Baczuk@gmail.com> | 2018-07-16 22:07:25 -0600 |
|---|---|---|
| committer | Jordan Baczuk <Jordan.Baczuk@gmail.com> | 2018-08-31 07:50:55 -0600 |
| commit | fb97437efa06acfbe75a5e34d8bbf8388d5f6432 (patch) | |
| tree | 91d82f3f19f476327d0745609f40e4301320df97 /doc/tor.md | |
| parent | b012bbe358311cc4a73300ccca41b64272250277 (diff) | |
added note that control port must be enabled and how to do that in torrc config file
Diffstat (limited to 'doc/tor.md')
| -rw-r--r-- | doc/tor.md | 7 |
1 files changed, 4 insertions, 3 deletions
diff --git a/doc/tor.md b/doc/tor.md index 2d0676c89a..dc0b88618a 100644 --- a/doc/tor.md +++ b/doc/tor.md @@ -93,7 +93,7 @@ API, to create and destroy 'ephemeral' hidden services programmatically. Bitcoin Core has been updated to make use of this. 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 +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 (`-listen`), and @@ -102,8 +102,9 @@ and, if not disabled, configured using the `-torcontrol` and `-torpassword` sett 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 -to the `CookieAuthFile` specified in Tor configuration. In some cases, this is +configured. It also requires the control socket to be enabled, e.g. put `ControlPort 9051` +in `torrc` config file. For cookie authentication the user running bitcoind must have read +access to the `CookieAuthFile` specified in Tor configuration. In some cases this is preconfigured and the creation of a hidden service is automatic. If permission problems are seen with `-debug=tor` they can be resolved by adding both the user running Tor and the user running bitcoind to the same group and setting permissions appropriately. On |