Merge #16857: doc: Elaborate need to re-login on Debian-based after usermod for Tor group
706340150f
Elaborate on the need to re-login on Debian-based systems to use tor following usermod (clashicly) Pull request description: Starting bitcoind with `-onlynet=onion` immediately after adding bitcoind user to debian-tor group will yield the following notice on debug.log: "tor: Authentication cookie /run/tor/control.authcookie could not be opened (check permissions)" Elaborate on the need to re-login to ensure debian-tor group has been applied to bitcoind user after: sudo usermod -a -G debian-tor username Verification can be done via `groups` command in shell. Otherwise operator may not be aware at first launch they are not running a tor enabled node. ACKs for top commit: fanquake: ACK706340150f
- Thanks for following up. Tree-SHA512: 3473966fb43b4f1c86bd8841dd6ea8c2798256c2ca926b10bd08cd655b954a9e77f0278c4fe63160e69cc75e240a3580af00ea46bf960fde2788aa88f03510b2
This commit is contained in:
commit
a199f75225
1 changed files with 4 additions and 1 deletions
|
@ -114,7 +114,10 @@ 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.
|
||||
which has the appropriate permissions. Before starting bitcoind you will need to re-login
|
||||
to allow debian-tor group to be applied. Otherwise you will see the following notice: "tor:
|
||||
Authentication cookie /run/tor/control.authcookie could not be opened (check permissions)"
|
||||
on debug.log.
|
||||
|
||||
An alternative authentication method is the use
|
||||
of the `-torpassword=password` option. The `password` is the clear text form that
|
||||
|
|
Loading…
Reference in a new issue