aboutsummaryrefslogtreecommitdiff
path: root/doc/release-notes.md
diff options
context:
space:
mode:
authorWladimir J. van der Laan <laanwj@gmail.com>2015-07-13 13:31:38 +0200
committerWladimir J. van der Laan <laanwj@gmail.com>2015-07-13 13:34:26 +0200
commit093729055358ecf155b74ce1b2870d3eb9064355 (patch)
tree56073db4857228c0c5f4ebd34f477851c39efb61 /doc/release-notes.md
parent71cbeaad9a929ba6a7b62d9b37a09b214ae00c1a (diff)
downloadbitcoin-093729055358ecf155b74ce1b2870d3eb9064355.tar.xz
doc: mention RPC random cookie authentication in release notes
Diffstat (limited to 'doc/release-notes.md')
-rw-r--r--doc/release-notes.md15
1 files changed, 15 insertions, 0 deletions
diff --git a/doc/release-notes.md b/doc/release-notes.md
index 6bb8587d78..d5ac70380f 100644
--- a/doc/release-notes.md
+++ b/doc/release-notes.md
@@ -4,6 +4,21 @@ release-notes at release time)
Notable changes
===============
+Random-cookie RPC authentication
+---------------------------------
+
+When no `-rpcpassword` is specified, the daemon now uses a special 'cookie'
+file for authentication. This file is generated with random content when the
+daemon starts, and deleted when it exits. Its contents are used as
+authentication token. Read access to this file controls who can access through
+RPC. By default it is stored in the data directory but its location can be
+overridden with the option `-rpccookiefile`.
+
+This is similar to Tor's CookieAuthentication: see
+https://www.torproject.org/docs/tor-manual.html.en
+
+This allows running bitcoind without having to do any manual configuration.
+
Example header
----------------------