aboutsummaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorsetpill <37372069+setpill@users.noreply.github.com>2019-08-06 16:48:10 +0200
committersetpill <37372069+setpill@users.noreply.github.com>2019-08-20 10:54:14 +0200
commitf3b57f4a1c17aadbf02d408e980490c88838c6ba (patch)
treeaf181bc6680a26cc05b50788e413a40b37181a1f /doc
parent870d4152dfc3d990e336723562948835c2dbd646 (diff)
downloadbitcoin-f3b57f4a1c17aadbf02d408e980490c88838c6ba.tar.xz
Unrecommend making config file owned by bitcoin
The bitcoin user needs read access to the configuration file, but write access is not needed. It is not considered best practice to make configuration directories and files owned by the services reading them.
Diffstat (limited to 'doc')
-rw-r--r--doc/init.md10
1 files changed, 5 insertions, 5 deletions
diff --git a/doc/init.md b/doc/init.md
index a6c9bb94d8..87e939c636 100644
--- a/doc/init.md
+++ b/doc/init.md
@@ -59,11 +59,11 @@ Data directory: `/var/lib/bitcoind`
PID file: `/var/run/bitcoind/bitcoind.pid` (OpenRC and Upstart) or `/run/bitcoind/bitcoind.pid` (systemd)
Lock file: `/var/lock/subsys/bitcoind` (CentOS)
-The configuration file, PID directory (if applicable) and data directory
-should all be owned by the bitcoin user and group. It is advised for security
-reasons to make the configuration file and data directory only readable by the
-bitcoin user and group. Access to bitcoin-cli and other bitcoind rpc clients
-can then be controlled by group membership.
+The PID directory (if applicable) and data directory should both be owned by the
+bitcoin user and group. It is advised for security reasons to make the
+configuration file and data directory only readable by the bitcoin user and
+group. Access to bitcoin-cli and other bitcoind rpc clients can then be
+controlled by group membership.
NOTE: When using the systemd .service file, the creation of the aforementioned
directories and the setting of their permissions is automatically handled by