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 Jun 11, 2024. It is now read-only.
Messages and requests which are too large should be rejected to prevent DoS against nodes. Ideally, this value should be configurable.
This is particularly important when dealing with peer info. Right now there is no limit as to how big the custom options object in P2PDiscoveredPeerInfo can be; so peers could just spam us with lots of data inside the options object to fill up our memory (since we keep a list of P2PDiscoveredPeerInfo).
Actual behavior
There is no size limit on messages and requests.
The text was updated successfully, but these errors were encountered:
jondubois
changed the title
Enforce limits on the new custom options field in P2P
Enforce limits on the size of inbound messages/requests in P2P
Feb 4, 2019
Expected behavior
Messages and requests which are too large should be rejected to prevent DoS against nodes. Ideally, this value should be configurable.
This is particularly important when dealing with peer info. Right now there is no limit as to how big the custom
options
object inP2PDiscoveredPeerInfo
can be; so peers could just spam us with lots of data inside the options object to fill up our memory (since we keep a list ofP2PDiscoveredPeerInfo
).Actual behavior
There is no size limit on messages and requests.
The text was updated successfully, but these errors were encountered: