doc: detail -rpccookieperms option

Co-authored-by: tdb3 <106488469+tdb3@users.noreply.github.com>
This commit is contained in:
willcl-ark 2024-04-22 12:24:09 +01:00
parent d2afa2690c
commit 73f0a6cbd0
No known key found for this signature in database
GPG key ID: CE6EC49945C17EA6

View file

@ -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.