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

Blacklist malicious nodes #1451

Open
herr-seppia opened this issue Aug 3, 2022 · 0 comments
Open

Blacklist malicious nodes #1451

herr-seppia opened this issue Aug 3, 2022 · 0 comments
Labels
area:p2p issues related to kadcast, peer, gossip mark:testnet type:rfc Changing the behaviour of something already defined

Comments

@herr-seppia
Copy link
Member

herr-seppia commented Aug 3, 2022

Describe what you want implemented
A mechanism for a node to stop receiving messages from well-known malicious nodes.

Describe "Why" this is needed
If a node receive malicious messages (kadcast wellformed but invalid) there is no way at the moment of writing to prevent processing further messages from the sender.
This can potentially lead to a DOS attack consuming cpu/memory/bandwidth.

Describe alternatives you've considered
N/A

Additional context
A solution at kadcast level would be great in order to remove the peer from the routing table (avoiding to even broadcast messages to it mitigating a partial network eclipse)
Blacklisting should be local to avoid to introduce any network-wide security issue

@herr-seppia herr-seppia added type:rfc Changing the behaviour of something already defined area:p2p issues related to kadcast, peer, gossip mark:testnet labels Aug 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:p2p issues related to kadcast, peer, gossip mark:testnet type:rfc Changing the behaviour of something already defined
Projects
None yet
Development

No branches or pull requests

1 participant