Clarify documentation for running a tor node
Previous wording suggested that no additional setup was required for a tor hidden service to be created.
This commit is contained in:
parent
ca5e229514
commit
4404073185
21
doc/tor.md
21
doc/tor.md
|
@ -98,17 +98,28 @@ 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.
|
||||||
Zcash has been updated to make use of this.
|
Zcash 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),
|
||||||
Zcash automatically creates a hidden service to listen on, without
|
Zcash automatically creates a hidden service to listen on. Zcash will also use Tor
|
||||||
manual configuration. Zcash will also use Tor automatically to connect
|
automatically to connect to other .onion nodes if the control socket can be
|
||||||
to other .onion nodes if the control socket can be successfully opened. This
|
successfully opened. This will positively affect the number of available .onion
|
||||||
will positively affect the number of available .onion nodes and their usage.
|
nodes and their usage.
|
||||||
|
|
||||||
This new feature is enabled by default if Zcash is listening, and
|
This new feature is enabled by default if Zcash 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 zcashd 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 zcashd to the same group and setting permissions appropriately. On
|
||||||
|
Debian-based systems the user running zcashd 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.
|
||||||
|
|
||||||
|
|
||||||
4. Connect to a Zcash hidden server
|
4. Connect to a Zcash hidden server
|
||||||
-----------------------------------
|
-----------------------------------
|
||||||
|
|
Loading…
Reference in New Issue