diff options
| author | willcl-ark <will@256k1.dev> | 2024-04-22 12:24:09 +0100 |
|---|---|---|
| committer | willcl-ark <will@256k1.dev> | 2024-06-27 15:08:27 +0100 |
| commit | 73f0a6cbd0b628675028fbd5a37eff8115e7ccfe (patch) | |
| tree | 37be25624c84fecc5103760e37d8ec5cada88aa7 | |
| parent | d2afa2690cceb0012b2aa1960e1cfa497f3103fa (diff) | |
doc: detail -rpccookieperms option
Co-authored-by: tdb3 <106488469+tdb3@users.noreply.github.com>
| -rw-r--r-- | doc/init.md | 6 |
1 files changed, 4 insertions, 2 deletions
diff --git a/doc/init.md b/doc/init.md index 7f79027718..d0b73593c0 100644 --- a/doc/init.md +++ b/doc/init.md @@ -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. |