Configuration section in doc/init.md says user must set rpcpassword in order to run bitcoind. Since 71cbea fixed the code to use a cookie for authentication, it is not mandatory to set rpcpassword in the configuration.
Fixes #16346
Configuration section in doc/init.md says user must set rpcpassword in order to run bitcoind. Since 71cbea fixed the code to use a cookie for authentication, it is not mandatory to set rpcpassword in the configuration.
Fixes #16346
19 | @@ -20,9 +20,9 @@ The macOS configuration assumes bitcoind will be set up for the current user. 20 | Configuration 21 | --------------------------------- 22 | 23 | -At a bare minimum, bitcoind requires that the rpcpassword setting be set 24 | -when running as a daemon. If the configuration file does not exist or this 25 | -setting is not set, bitcoind will shut down promptly after startup. 26 | +Running bitcoind as a daamon does not require any manual configuration. You may
nit: daemon, not daamon
my bad, will fix it
19 | @@ -20,9 +20,9 @@ The macOS configuration assumes bitcoind will be set up for the current user. 20 | Configuration 21 | --------------------------------- 22 | 23 | -At a bare minimum, bitcoind requires that the rpcpassword setting be set 24 | -when running as a daemon. If the configuration file does not exist or this 25 | -setting is not set, bitcoind will shut down promptly after startup. 26 | +Running bitcoind as a daamon does not require any manual configuration. You may 27 | +set the rpcpassword setting in the `bitcoin.conf` configuration file to override
nit: I personally prefer "overwrite"
technically this is an "override" because it is changing a default behavior and not replacing(overwrite) something that is existing.
Also override terminology is being used in other places -> https://github.com/bitcoin/bitcoin/blob/9546a785953b7f61a3a50e2175283cbf30bc2151/doc/bitcoin-conf.md
so to be consistent, guess it is okay to keep it "override".
19 | @@ -20,9 +20,9 @@ The macOS configuration assumes bitcoind will be set up for the current user. 20 | Configuration 21 | --------------------------------- 22 | 23 | -At a bare minimum, bitcoind requires that the rpcpassword setting be set 24 | -when running as a daemon. If the configuration file does not exist or this 25 | -setting is not set, bitcoind will shut down promptly after startup. 26 | +Running bitcoind as a daemon does not require any manual configuration. You may 27 | +set the rpcpassword setting in the `bitcoin.conf` configuration file to override 28 | +the default behaviour of using a special cookie for authentication.
Maybe give the (relative) path for cookie file
There is a dedicated doc/files.md file on this purpose in the repo.
Concept ACK. @jkcd Thank you for working on the docs.
Let me share two notes.
Note 1. There are three mechanisms to authenticate with:
.cookie file-rpcuser and -rpcpassword options to the RPC server (should be deprecated as a plain text RPC password is exposed). If -rpcuser is omitted, an empty string is used instead.-rpcauth option to the RPC serverMore details could be found in #15989 discussion.
Note 2. It is not necessary, but it is convenient, to provide authentication options in the bitcoin.conf file. They could be passed as the command line options as well.
Concept ACK, though I think in a lot of system-wide installs it's preferable to use RPC accounts instead of the cookie to have finer-grained access control, it might be good to mention the possibility.
@hebasto @laanwj thanks for your notes and comments.
Given that init.md only talks about configuration for bitcoind, calling out minimum configuration and not specifying command line options would suffice? or are you suggesting I add details for "either setting -rpcpassword in bitcoind.conf or using -rpcauth command line option" as part of this PR? I am assuming we don't have to specify -rpcuser and -rpcpassword command line option since it is deprecated. Please call out if changes are required so I can update the PR.
I don't think we should mention rpcpassword at all anymore; rpcauth should be preferable in all cases.
19 | @@ -20,9 +20,9 @@ The macOS configuration assumes bitcoind will be set up for the current user. 20 | Configuration 21 | --------------------------------- 22 | 23 | -At a bare minimum, bitcoind requires that the rpcpassword setting be set 24 | -when running as a daemon. If the configuration file does not exist or this 25 | -setting is not set, bitcoind will shut down promptly after startup. 26 | +Running bitcoind as a daemon does not require any manual configuration. You may 27 | +set the rpcpassword setting in the `bitcoin.conf` configuration file to override
set the `rpcauth` setting in the `bitcoin.conf` configuration file to override
19 | @@ -20,9 +20,9 @@ The macOS configuration assumes bitcoind will be set up for the current user. 20 | Configuration 21 | --------------------------------- 22 | 23 | -At a bare minimum, bitcoind requires that the rpcpassword setting be set 24 | -when running as a daemon. If the configuration file does not exist or this 25 | -setting is not set, bitcoind will shut down promptly after startup. 26 | +Running bitcoind as a daemon does not require any manual configuration. You may 27 | +set the `rpcauth` setting in the `bitcoin.conf` configuration file to override
nit (feel free to ignore):
set the [`rpcauth` setting](/share/rpcauth) in the `bitcoin.conf` configuration file to override
ACK
Please squash your commits according to https://github.com/bitcoin/bitcoin/blob/master/CONTRIBUTING.md#squashing-commits
ACK a2a03c3ca94b1cdd279ac09f2a81e04d262586fd, modulo nit
Can be improved upon later on, going to merge this improvement now.