Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
Already on GitHub? Sign in to your account
Bitcoind 'first run' steps are out of date for configuring RPC auth #1217
Comments
|
This is is only in 0.12+, which is not yet a released version. I agree cookie auth could be mentioned, but for people using older versions the old instructions are still useful. |
harding
self-assigned this
Jan 22, 2016
harding
added
the
Core
label
Jan 24, 2016
harding
removed their assignment
Feb 10, 2016
|
(Noting that 0.12.0 was released: https://github.com/bitcoin/bitcoin/blob/v0.12.0/doc/release-notes.md#rpc-random-cookie-rpc-authentication) |
wbnns
self-assigned this
Dec 9, 2016
wbnns
added
the
Under Review
label
Dec 20, 2016
wbnns
added
Merge Scheduled
and removed
Under Review
labels
Dec 28, 2016
wbnns
closed this
Jan 1, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
seusher commentedJan 22, 2016
The steps for setting up bitcoind (https://bitcoin.org/en/full-node#ubuntu-daemon) currently tell you to wait for the message giving you your rpcuser and rpcpassword parameters:
rpcuser=bitcoinrpc
rpcpassword=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
bitcoind no longer does this since it generates a local rpc authentication cookie. These steps should be updated to inform the user of the rcp auth cookie and let them know they aren’t required to set their own password anymore.