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

rpc_allow instead of rpc_allow_remote #175

Closed
dokterbob opened this issue Oct 11, 2013 · 1 comment
Closed

rpc_allow instead of rpc_allow_remote #175

dokterbob opened this issue Oct 11, 2013 · 1 comment

Comments

@dokterbob
Copy link

Currently, it is only possible to enable/disable RPC access for 127.0.0.1 rather than being able to specify exactly which address or addresses have access - while for admin-specific commands this is already possible. I would like to propose instead having rpc_allow with a similar syntax as rpc_admin_allow.

This is related to #170 and #174 but is more of a suggested improvement rather than a bugfix; in a lot of cases we want to open up the RPC interface just to a particular network (ie. DMZ, VPN) for just a particular address or a particular group of addresses. Moreover, this would allow for the OS to handle whether or not a socket can be established (rather than rippled itself as with rpc_allow_remote), potentially increasing security.

@vinniefalco
Copy link
Contributor

Obsolete

tequdev pushed a commit to tequdev/rippled that referenced this issue Nov 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants