-
Notifications
You must be signed in to change notification settings - Fork 0
_posts: LND: Excessive Failback Exploit #2 #11
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
Conversation
|
@Arvin21M: ready for review! |
Arvin21M
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- Just one or two very minor edit requests.
- Otherwise, this reads well, and looks good to go!

|
|
||
| ## The Variant Bug | ||
|
|
||
| While a fix for the original excessive failback bug was included in LND 0.18.0, a minor variant of the bug was missed when the channel was force closed using LND's commitment instead of the attacker's. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| While a fix for the original excessive failback bug was included in LND 0.18.0, a minor variant of the bug was missed when the channel was force closed using LND's commitment instead of the attacker's. | |
| While a fix for the original excessive failback bug was included in LND 0.18.0, a minor variant of the bug remained when the channel was force closed using LND's commitment instead of the attacker's. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done.
| ## Discovery | ||
|
|
||
| This variant was discovered shortly after the original disclosure, while I was [updating](https://github.com/lightning/bolts/pull/1233) BOLT 5 to prevent future excessive failback vulnerabilities. | ||
| I realized there were actually *two* cases that needed to be updated in BOLT 5, while only one of the cases had been patched in LND. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| I realized there were actually *two* cases that needed to be updated in BOLT 5, while only one of the cases had been patched in LND. | |
| I realized there were actually *two* cases that needed to be updated in BOLT 5, but only one of the cases had been patched in LND. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done.
bf9e810 to
69db962
Compare
No description provided.