diff options
| author | clashicly <35277077+clashicly@users.noreply.github.com> | 2019-09-12 00:55:05 -0400 |
|---|---|---|
| committer | clashic <clashic@fullnodenocix2.clashic.cash> | 2019-09-12 08:27:03 -0500 |
| commit | 706340150f3ae26fce4659f8fa0a5d57149d2fb3 (patch) | |
| tree | 09622bfd85e044799ef1b15a1fa18d23d4b97fce /doc | |
| parent | 2324aa1dc409e9496b7083aaef5fcb20849f33c0 (diff) | |
| download | bitcoin-706340150f3ae26fce4659f8fa0a5d57149d2fb3.tar.xz | |
Elaborate on the need to re-login on Debian-based systems to use tor following usermod
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.
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/tor.md | 5 |
1 files changed, 4 insertions, 1 deletions
diff --git a/doc/tor.md b/doc/tor.md index cfb7f16666..2c54e32f84 100644 --- a/doc/tor.md +++ b/doc/tor.md @@ -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 |