aboutsummaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorChakib Benziane <chakib.benz@gmail.com>2018-10-30 15:58:51 +0100
committerfanquake <fanquake@gmail.com>2018-11-26 08:45:32 +0800
commit6c6ee8af80cdd6bc3b677b95209b0700f08a2c98 (patch)
tree0de5b0bbc29689b0c85868b78e83c04dfc1062a3 /doc
parent327129f7a6440e3bbd0a0ea415ea5f8907cf3233 (diff)
Less confusing documentation for `torpassword`
The current documentation leads the reader to think `hash-password` is an other option. This change is less confusing and make it clear how to use this option.
Diffstat (limited to 'doc')
-rw-r--r--doc/tor.md10
1 files changed, 7 insertions, 3 deletions
diff --git a/doc/tor.md b/doc/tor.md
index dc0b88618a..c46b7e9f60 100644
--- a/doc/tor.md
+++ b/doc/tor.md
@@ -109,9 +109,13 @@ preconfigured and the creation of a hidden service is automatic. If permission p
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
Debian-based systems the user running bitcoind can be added to the debian-tor group,
-which has the appropriate permissions. An alternative authentication method is the use
-of the `-torpassword` flag and a `hash-password` which can be enabled and specified in
-Tor configuration.
+which has the appropriate permissions.
+
+An alternative authentication method is the use
+of the `-torpassword=password` option. The `password` is the clear text form that
+was used when generating the hashed password for the `HashedControlPassword` option
+in the tor configuration file. The hashed password can be obtained with the command
+`tor --hash-password password` (read the tor manual for more details).
## 4. Privacy recommendations