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.

Sign up for GitHub

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

Jump to bottom

rpcserver: Impose additional read limits. #2675

Merged
merged 2 commits into from
Jul 5, 2021
Merged

rpcserver: Impose additional read limits. #2675

merged 2 commits into from
Jul 5, 2021

Commits on Jun 30, 2021

  1. rpcserver: Impose additional read limits. 

    This imposes additional per-connection read limits on the RPC server to
help further harden it against potential abuse in non-standard
configurations on poorly-configured networks.

In practice, these changes will not have any noticeable effect for the
vast majority of nodes since the RPC server is not publicly accessible
by default and requires authentication.

Nevertheless, it can still be useful to apply additional read limits for
scenarios such as authenticated fuzz testing and poorly-configured
networks that have disabled all other security measures.

The following are the updated per-connection limits:

- 0 B / 8 MiB for pre and post auth HTTP connections
- 4 KiB / 16 MiB for pre and post auth websocket connections
    @davecgh
    davecgh committed Jun 30, 2021
    Configuration menu
    Copy the full SHA
    611e50a View commit details
    Browse the repository at this point in the history

  2. docs: Update JSON-RPC API for max request limits.

    @davecgh
    davecgh committed Jun 30, 2021
    Configuration menu
    Copy the full SHA
    2e8efe1 View commit details
    Browse the repository at this point in the history