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

htlcswitch+lnwallet: ReceiveMalformedFailHTLC #7030

Closed

Conversation

joostjager
Copy link
Contributor

@joostjager joostjager commented Oct 13, 2022

Reviving a three year old idea described in #3027 (comment).

Variable failure length messages force us to rethink the previously chosen solution that depends on a fixed length, see #6913

// to an actual error, by encrypting it as if we were
// the originating hop.
convertedErrorSize := lnwire.FailureMessageLength + 4
if len(pd.FailReason) == convertedErrorSize {
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Need to think about this deletion in the context of upgrade scenarios with lingering 'old style' malformed fails.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Migrating Fail to MalformedFail for the pending updates in the channel db doesn't look very attractive.

@joostjager
Copy link
Contributor Author

In #6913 (comment), we decided to simply not allow failure messages shorter than 256 bytes. Closing this for now.

@joostjager joostjager closed this Dec 14, 2022
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.

1 participant