-
Notifications
You must be signed in to change notification settings - Fork 1k
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
protocols/identify: Validate addresses before caching #2302
Comments
Do we want to treat validation errors as bad behaviour and disconnect from that peer? |
For now I would suggest we just ignore those addresses with a peer ID mismatch in Reasoning: Maybe there is a benign way (in old versions) how this could happen. Disconnecting on mismatch might lead to large disconnects in live networks. Without measuring this beforehand, I would deem this change too risky. Do you have some time to file a patch? I am sorry, I am a bit low on time / energy (sick). If not, I can just set the default value of |
Not at the moment but I am okay with disabling the current behaviour if it causes problems. |
See libp2p#2302 for details.
@thomaseizinger I'll pick this up unless you're working on it, thanks! |
Go for it! I haven't started on this yet :) |
With #2232
libp2p-identify
caches discovered listen addresses to provide additional addresses when dialing a peer viaNetworkBehaviour::addresses_of_peer
.Before caching received listen addresses,
libp2p-identify
should validate these addresses. Validations:/p2p/QmXXX
make sureQmXX
matches the peer'sPeerId
.//CC @AgeManning: This might be the reason for the dial failures you are seeing.
The text was updated successfully, but these errors were encountered: