sikkienl/dash
1
0
Fork 0
mirror of https://github.com/dashpay/dash.git synced 2024-12-27 13:03:17 +01:00
Code Issues Actions Packages Projects Releases Wiki Activity

Merge #8203: Clarify documentation for running a tor node

Browse Source 
9e3ec74 Clarify documentation for running a tor node (Nathaniel Mahieu)
This commit is contained in:
Wladimir J. van der Laan 2016-06-20 10:48:07 +02:00
commit 377d1310ac
No known key found for this signature in database
GPG Key ID: 74810B012346C9A6
1 changed files with 14 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
doc/tor.md
View File

@ -95,12 +95,22 @@ Starting with Tor version 0.2.7.1 it is possible, through Tor's control socket
API, to create and destroy 'ephemeral' hidden services programmatically. API, to create and destroy 'ephemeral' hidden services programmatically.
Bitcoin Core has been updated to make use of this. Bitcoin Core has been updated to make use of this.
This means that if Tor is running (and proper authorization is available), This means that if Tor is running (and proper authentication has been configured),
Bitcoin Core automatically creates a hidden service to listen on, without Bitcoin Core automatically creates a hidden service to listen on. This will positively
manual configuration. This will positively affect the number of available affect the number of available .onion nodes.
.onion nodes.
This new feature is enabled by default if Bitcoin Core is listening, and 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`, a connection to Tor can be made. It can be configured with the `-listenonion`,
`-torcontrol` and `-torpassword` settings. To show verbose debugging `-torcontrol` and `-torpassword` settings. To show verbose debugging
information, pass `-debug=tor`. 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
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
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.