fix(keystore): await aborted relock task in lock()#468
Open
ouicate wants to merge 1 commit into
Open
Conversation
KeyStore::lock() aborted the background relock task but did not await its completion, unlike unlock(). A rapid walletpassphrase after walletlock could therefore leave the wallet locked despite reporting success when the stale task cleared identities after unlock() repopulated them. Fixes GHSA-8cfr-hmvc-2333. Co-Authored-By: Cursor <cursoragent@cursor.com>
Author
|
Please review @nullcopy |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
KeyStore::lock()now awaits aborted relock tasks before clearing identities, matching the existingunlock()behavior.walletpassphraseafterwalletlockcould report success while leaving the wallet locked, because a stale relock task could clear identities afterunlock()repopulated them.