diff options
| author | fanquake <fanquake@gmail.com> | 2019-09-13 10:43:26 +0800 |
|---|---|---|
| committer | fanquake <fanquake@gmail.com> | 2019-09-13 11:27:51 +0800 |
| commit | a199f75225897d3f10c9ef71fd8117664dc32a60 (patch) | |
| tree | 272e666c410cac567cb0a4189df266c891332ffa /src | |
| parent | 884f7cc81b478b599ed8d43ebe80578ea9cdb279 (diff) | |
| parent | 706340150f3ae26fce4659f8fa0a5d57149d2fb3 (diff) | |
Merge #16857: doc: Elaborate need to re-login on Debian-based after usermod for Tor group
706340150f3ae26fce4659f8fa0a5d57149d2fb3 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:
ACK 706340150f3ae26fce4659f8fa0a5d57149d2fb3 - Thanks for following up.
Tree-SHA512: 3473966fb43b4f1c86bd8841dd6ea8c2798256c2ca926b10bd08cd655b954a9e77f0278c4fe63160e69cc75e240a3580af00ea46bf960fde2788aa88f03510b2
Diffstat (limited to 'src')
0 files changed, 0 insertions, 0 deletions