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.
This commit is contained in:
setpill 2019-08-06 16:48:10 +02:00
parent 870d4152df
commit f3b57f4a1c

View File

@ -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) PID file: `/var/run/bitcoind/bitcoind.pid` (OpenRC and Upstart) or `/run/bitcoind/bitcoind.pid` (systemd)
Lock file: `/var/lock/subsys/bitcoind` (CentOS) Lock file: `/var/lock/subsys/bitcoind` (CentOS)
The configuration file, PID directory (if applicable) and data directory The PID directory (if applicable) and data directory should both be owned by the
should all be owned by the bitcoin user and group. It is advised for security bitcoin user and group. It is advised for security reasons to make the
reasons to make the configuration file and data directory only readable by the configuration file and data directory only readable by the bitcoin user and
bitcoin user and group. Access to bitcoin-cli and other bitcoind rpc clients group. Access to bitcoin-cli and other bitcoind rpc clients can then be
can then be controlled by group membership. controlled by group membership.
NOTE: When using the systemd .service file, the creation of the aforementioned NOTE: When using the systemd .service file, the creation of the aforementioned
directories and the setting of their permissions is automatically handled by directories and the setting of their permissions is automatically handled by