Correctly randomize value buffer #172
Merged
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
YaacovHazan
reviewed
Mar 21, 2022
Collaborator
|
@caipengbo LGTM, did you test it? |
Contributor
Author
|
@YaacovHazan Yeah, I've tested it :) |
YaacovHazan
approved these changes
Mar 30, 2022
Contributor
Author
|
CI seems to have some problems. |
Collaborator
|
Thanks @caipengbo |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
The current logic for randomizing value_buffer looks like something's wrong, and I've tried to fix it.
I guess the original intent was to read the
/dev/urandomfile every20*64*64bytes, and I modified it to follow this logic.Related issue #171.