Zero scrypt scratch buffers before freeing#414
Open
albertoblancas123 wants to merge 1 commit into
Open
Conversation
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
Zero the scratch buffers used by
crypto_scrypt()before releasing them:B,XY, andVin the reference implementationB,XY, andVin the platform implementationThis uses the existing
insecure_memzero()helper already linked by the project.Refs Tarsnap/tarsnap#703.
Validation
git diff --check HEAD~1 HEADsmixstorage contract and zeroed the full256 * r + 64XYregion in the platform implementation.I could not run
autoreconf && ./configure && make testlocally because this Windows environment does not have the C/autotools toolchain installed and WSL is not installed.