Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for secure (.cookie) auth #118

Open
moodmosaic opened this issue Jan 15, 2021 · 0 comments
Open

Add support for secure (.cookie) auth #118

moodmosaic opened this issue Jan 15, 2021 · 0 comments

Comments

@moodmosaic
Copy link
Contributor

By default, 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 automatically.

The auth file is named .cookie and it's auto-generated in the Bitcoin Core data directory. Using the auto-generated credentials from the .cookie file is the preferred RPC authentication method.

As a fallback, one can directly use manually-chosen rpcuser and rpcpassword configuration parameters, but he or she must ensure that those are strong and unique (and still don't use insecure networks).

Based on configuration settings, bitcoinlib should be able to use either the .cookie or the manually-chosen rpcuser and rpcpassword.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant