-
Notifications
You must be signed in to change notification settings - Fork 221
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
fix: ban peers if they send a bad protobuf message #5693
fix: ban peers if they send a bad protobuf message #5693
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good. I just have a NIT about IllFormed, as camel case that just reads difficult.
There are some uncommented code to be deleted.
And I created issues for the todos. Todos left in code will stay there, and later get deleted. A todo worth doing, is worth creating a issue for
Co-authored-by: SW van Heerden <[email protected]>
Co-authored-by: SW van Heerden <[email protected]>
Co-authored-by: SW van Heerden <[email protected]>
Co-authored-by: SW van Heerden <[email protected]>
Co-authored-by: SW van Heerden <[email protected]>
Co-authored-by: SW van Heerden <[email protected]>
Co-authored-by: SW van Heerden <[email protected]>
Description
Propagate errors in decoding protobuf messages and conversions higher up so that nodes can ban them
Motivation and Context
Bad messages were previously ignored and could just fill up a node's buffers. This PR allows the nodes to ban more messages from those peers.
How Has This Been Tested?
Tested locally and cargo test
What process can a PR reviewer use to test or verify this change?
This is pretty tough to test, you might have to try connect an old node to this peer
Breaking Changes