-
Notifications
You must be signed in to change notification settings - Fork 35.4k
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
RPC: add/remove -rpcallowip and -rpcauth options without restart #16543
Comments
For your second point, are you thinking of adding a separate config parameter for disabling an rpc shutdown? |
See #16544. This could fix your second point |
Could be related: #12248 |
I have a project that does something similar to this, it can be configured to fit your use case I believe. |
This is a duplicate of #12248? If not, it should specify how this feature request is different. |
Ok, maybe create a separate issue for that? A title of "feature request" with two features in the comment body isn't helpful to keep track of issues. |
OP has been updated. |
Running the Bitcoin Core at a university for research purposes. Researchers use RPC to have an access to the Bitcoin Core via a LAN. Their credentials are stored in the
bitcoin.conf
file as pairs ofrpcallowip=<ip>
andrpcauth=<userpw>
options.From the Core operator's point of view, it seems
two features area feature is missing:-rpcallowip
and-rpcauth
options without the Bitcoin Core restartpreventing to stop the Bitcoin Core from a remote machine bybitcoin-cli stop
(a special case of a more general RPC Whitelist Files #12248)The text was updated successfully, but these errors were encountered: