You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 24, 2022. It is now read-only.
In some cases we may need to close some API methods leaving others available. For example, for enabled eth namespace we could restrict eth_sendTransaction.
I'd propose to add
--jsonrpc-restricted-methods
CLI option (and a similar --ws-restricted-methods for WebSocket connections).
Such an option would close access for the listed methods for all network interfaces and ports. I think we don't need to delimit them by ip/port.
If --ws-restricted-methods is not defined, its value would be implicitly taken from --jsonrpc-restricted-methods for the case when a user forgot to restrict the same methods for WebSockets (and vice versa).
The text was updated successfully, but these errors were encountered:
UPD: probably, it's better to make an opposite behaviour like it's implemented in Nethermind in CallsFilterFilePath option which whitelists approved JSON RPC methods.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
In some cases we may need to close some API methods leaving others available. For example, for enabled
eth
namespace we could restricteth_sendTransaction
.I'd propose to add
CLI option (and a similar
--ws-restricted-methods
for WebSocket connections).The method names are comma-separated, e.g.:
Such an option would close access for the listed methods for all network interfaces and ports. I think we don't need to delimit them by ip/port.
If
--ws-restricted-methods
is not defined, its value would be implicitly taken from--jsonrpc-restricted-methods
for the case when a user forgot to restrict the same methods for WebSockets (and vice versa).The text was updated successfully, but these errors were encountered: