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

channeld/channeld.c: Log and ignore repeated WIRE_CHANNEL_REESTABLISH. #3964

Merged

Conversation

ZmnSCPxj
Copy link
Collaborator

Fixes: #3608

Changelog-Changed: protocol: Ignore (and log as "unusual") repeated WIRE_CHANNEL_REESTABLISH messages, to be compatible with buggy peer software that sometimes does this.

Fixes: ElementsProject#3608

Changelog-Changed: protocol: Ignore (and log as "unusual") repeated `WIRE_CHANNEL_REESTABLISH` messages, to be compatible with buggy peer software that sometimes does this.
@ZmnSCPxj
Copy link
Collaborator Author

No idea how to test this tho.

@rustyrussell rustyrussell merged commit a1ba214 into ElementsProject:master Aug 28, 2020
@whitslack
Copy link
Collaborator

It honestly seems bonkers to me that the Lightning peer-wire protocol doesn't allow NAK'ing protocol messages in any way that allows the channel to remain open. How can we expect to achieve interoperability when implementations are utterly unable to say, "I disagree with (or did not understand) the message you just sent, so I will take no action, and you need not either"?

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.

Channel closed because WIRE_CHANNEL_REESTABLISH is an unknown message?
3 participants