mirror of
https://github.com/dashpay/dash.git
synced 2024-12-25 20:12:57 +01:00
Merge #8203: Clarify documentation for running a tor node
9e3ec74
Clarify documentation for running a tor node (Nathaniel Mahieu)
This commit is contained in:
parent
b6d8206c20
commit
05684db6e3
18
doc/tor.md
18
doc/tor.md
@ -122,12 +122,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.
|
||||||
Dash Core has been updated to make use of this.
|
Dash 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),
|
||||||
Dash Core automatically creates a hidden service to listen on, without
|
Dash 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 Dash Core is listening, and
|
This new feature is enabled by default if Dash 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 dashd 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 dashd to the same group and setting permissions appropriately. On
|
||||||
|
Debian-based systems the user running dashd 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.
|
Loading…
Reference in New Issue
Block a user