Skip to content

Conversation

@crazybits
Copy link

@crazybits crazybits commented Sep 15, 2025

refer to the latest fullnode config, there are p2p-max-nodes-per-host = 100 and max-clients = 100, with this config, the malicious node could occupy all the incoming connections of the target node with one node to make others unable to connect the target node that will be harmful to the network healthy, the correct config may be p2p-max-nodes-per-host = 2

refer to the latest fullnode config, there are p2p-max-nodes-per-host = 100 and max-clients = 100, in this config, the malicious node could use one node to occupy all the incoming connections of the target node to make others unable to connect the node which will be harmful to the network healthy, the correct config may be p2p-max-nodes-per-host = 2 and max-clients = 100
@paulgnz
Copy link
Collaborator

paulgnz commented Jan 22, 2026

This security fix has been incorporated into PR #20 which also adds a P2P peer discovery script and verified peer list. Recommend merging #20 instead and closing this PR.

@paulgnz
Copy link
Collaborator

paulgnz commented Jan 22, 2026

Closing: The security fix in this PR has been merged via PR #20, which also includes additional improvements (P2P discovery script and verified peer list).

@paulgnz paulgnz closed this Jan 22, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants