fix view key corruption - #436
Open
auruya wants to merge 1 commit into
Open
Conversation
Collaborator
|
This is the job of the |
Author
|
@jeffro256 yes that can be another way to solve it. If that is preferred, I think this Line 3651 in 18b0c9f Line 3673 in 18b0c9f |
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
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.
Since the output scanning is done in parallel to key image calculation now, we sometimes get a scrambled view key due to a race condition where view key gets read by scan job between the time we encrypt view key before decrypting all keys. This PR adds a couple of new functions to
account_keysthat excludes view key encryption/decryption directly instead of encrypting/decrypting it each time.