From 3f5588f0b74a57734d0bc7900ccfff379dc6c2ae Mon Sep 17 00:00:00 2001 From: "Wladimir J. van der Laan" Date: Sun, 2 Sep 2018 10:38:11 +0200 Subject: [PATCH] Merge #14120: Notes about control port and read access to cookie fb97437 added note that control port must be enabled and how to do that in torrc config file (Jordan Baczuk) Pull request description: Reopened from bitcoin#13681 because pushes made it unable to reopen. Tree-SHA512: 34eac14308aef70963b630173cd93916201553d5323ab2de3517d4a78604ae5a7cf8691a314c0af00fe36f0ef19b94a4c371d2e7aa1229d9c603d36c51b115fb --- doc/tor.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/doc/tor.md b/doc/tor.md index 733baab43d..fd28d24c20 100644 --- a/doc/tor.md +++ b/doc/tor.md @@ -120,7 +120,7 @@ API, to create and destroy 'ephemeral' hidden services programmatically. Dash Core has been updated to make use of this. This means that if Tor is running (and proper authentication has been configured), -Dash Core automatically creates a hidden service to listen on. This will positively +Dash 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 Dash Core is listening (`-listen`), and @@ -129,8 +129,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 dashd 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 dashd 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 dashd to the same group and setting permissions appropriately. On