diff options
| author | fanquake <fanquake@gmail.com> | 2015-08-07 11:35:15 +0800 |
|---|---|---|
| committer | fanquake <fanquake@gmail.com> | 2015-08-10 23:56:37 +0800 |
| commit | 8778471dceb01e3ace825bdb5a3f59ff8d6f2b4f (patch) | |
| tree | 1793418c4813b59b596696738a4ab47d5b508d3f /doc | |
| parent | 0201a79299f782193897d3ba2d7a2904fa4c11ea (diff) | |
Update init doc to mention cookie authentication
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/init.md | 12 |
1 files changed, 7 insertions, 5 deletions
diff --git a/doc/init.md b/doc/init.md index 7dee450c29..ed9ce72154 100644 --- a/doc/init.md +++ b/doc/init.md @@ -29,13 +29,15 @@ file, however it is recommended that a strong and secure password be used as this password is security critical to securing the wallet should the wallet be enabled. -If bitcoind is run with "-daemon" flag, and no rpcpassword is set, it will -print a randomly generated suitable password to stderr. You can also -generate one from the shell yourself like this: +If bitcoind is run with the "-server" flag (set by default), and no rpcpassword is set, +it will use a special cookie file for authentication. The cookie is generated with random +content when the daemon starts, and deleted when it exits. Read access to this file +controls who can access it through RPC. -`bash -c 'tr -dc a-zA-Z0-9 < /dev/urandom | head -c32 && echo'` +By default the cookie is stored in the data directory, but it's location can be overridden +with the option '-rpccookiefile'. -Once you have a password in hand, set `rpcpassword=` in `/etc/bitcoin/bitcoin.conf` +This allows for running bitcoind without having to do any manual configuration. `conf`, `pid`, and `wallet` accept relative paths which are interpreted as relative to the data directory. `wallet` *only* supports relative paths. |