aboutsummaryrefslogtreecommitdiff
path: root/doc/JSON-RPC-interface.md
diff options
context:
space:
mode:
authoriamcarlos94 <62184065+iamcarlos94@users.noreply.github.com>2023-08-17 13:46:18 +0100
committerGitHub <noreply@github.com>2023-08-17 13:46:18 +0100
commitbdb2e8d4aef927efd4e74d31b5d4dffe73470d1f (patch)
treec17ea87e358f9c5f76817b072c0e7451fca5ed1b /doc/JSON-RPC-interface.md
parent6d473bad2260fd23c6013581e44c9970b557f495 (diff)
downloadbitcoin-bdb2e8d4aef927efd4e74d31b5d4dffe73470d1f.tar.xz
Update JSON-RPC-interface.md
clarifying when the .cookie file is generated
Diffstat (limited to 'doc/JSON-RPC-interface.md')
-rw-r--r--doc/JSON-RPC-interface.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/JSON-RPC-interface.md b/doc/JSON-RPC-interface.md
index 6cbb6ebd72..ec332d23eb 100644
--- a/doc/JSON-RPC-interface.md
+++ b/doc/JSON-RPC-interface.md
@@ -128,7 +128,7 @@ RPC interface will be abused.
Instead, expose it only on the host system's localhost, for example:
`-p 127.0.0.1:8332:8332`
-- **Secure authentication:** By default, Bitcoin Core generates unique
+- **Secure authentication:** By default, when no `rpcpassword` is specified, Bitcoin Core generates unique
login credentials each time it restarts and puts them into a file
readable only by the user that started Bitcoin Core, allowing any of
that user's RPC clients with read access to the file to login