mirror of
https://github.com/bitcoin/bitcoin.git
synced 2025-06-29 18:20:58 +02:00
Merge bitcoin/bitcoin#28167: init: Add option for rpccookie permissions (replace 26088)
73f0a6cbd0
doc: detail -rpccookieperms option (willcl-ark)d2afa2690c
test: add rpccookieperms test (willcl-ark)f467aede78
init: add option for rpccookie permissions (willcl-ark)7df03f1a92
util: add perm string helper functions (willcl-ark) Pull request description: This PR picks up #26088 by aureleoules which adds a bitcoind launch option `-rpccookieperms` to set the file permissions of the cookie generated by bitcoin core. Example usage to make the generated cookie group-readable: `./src/bitcoind -rpccookieperms=group`. Accepted values for `-rpccookieperms` are `[owner|group|all]`. We let `fs::perms` handle platform-specific permissions changes. ACKs for top commit: achow101: ACK73f0a6cbd0
ryanofsky: Code review ACK73f0a6cbd0
. Main change since last review is no longer throwing a skip exception in the rpc test on windows, so other checks can run after it, and overall test result is passing, not skipped. Also were clarifying renames and documentation improvements. tdb3: cr ACK73f0a6cbd0
Tree-SHA512: e800d59a44aca10e1c58ca69bf3fdde9f6ccf5eab4b7b962645af6d6bc0cfa3a357701e409c8c60d8d7744fcd33a91e77ada11790aa88cd7811ef60fab86ab11
This commit is contained in:
@ -35,8 +35,10 @@ it will use a special cookie file for authentication. The cookie is generated wi
|
||||
content when the daemon starts, and deleted when it exits. Read access to this file
|
||||
controls who can access it through RPC.
|
||||
|
||||
By default the cookie is stored in the data directory, but it's location can be overridden
|
||||
with the option '-rpccookiefile'.
|
||||
By default the cookie is stored in the data directory, but its location can be
|
||||
overridden with the option `-rpccookiefile`. Default file permissions for the
|
||||
cookie are "owner" (i.e. user read/writeable) via default application-wide file
|
||||
umask of `0077`, but these can be overridden with the `-rpccookieperms` option.
|
||||
|
||||
This allows for running bitcoind without having to do any manual configuration.
|
||||
|
||||
|
Reference in New Issue
Block a user