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

Support specifying rpcpassword by file #148

Closed
basvandijk opened this issue Mar 24, 2017 · 3 comments
Closed

Support specifying rpcpassword by file #148

basvandijk opened this issue Mar 24, 2017 · 3 comments
Labels
upstream bug A bug that is (likely) present also in upstream Bitcoin and should be fixed there.

Comments

@basvandijk
Copy link

Currently the rpcpassword must be specified in the namecoin.conf configuration file. On some systems (for example in NixOS) configuration files are stored in world-readable locations. It's a bad idea to store secrets in world-readable locations.

To better support these systems it would be nice if there was a rpcpasswordFile configuration parameter. Users can then keep namecoin.conf in a world-readable location but set rpcpasswordFile to a file with restricted ownership and permissions.

@JeremyRand
Copy link
Member

JeremyRand commented Mar 24, 2017 via email

@basvandijk
Copy link
Author

Good tip! I created: bitcoin/bitcoin#10071.

@domob1812 domob1812 added the upstream bug A bug that is (likely) present also in upstream Bitcoin and should be fixed there. label Jun 5, 2018
@domob1812
Copy link

Closing this, since it is indeed an upstream issue (and was already brought up with Bitcoin). Also, as mentioned in the Bitcoin issue, there are now alternatives to password authentication (e. g., cookie files).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
upstream bug A bug that is (likely) present also in upstream Bitcoin and should be fixed there.
Projects
None yet
Development

No branches or pull requests

3 participants