Fix and test correctness of constant_time_conditional_memxor on GCC#2734
Closed
ctz wants to merge 2 commits intobriansmith:mainfrom
Closed
Fix and test correctness of constant_time_conditional_memxor on GCC#2734ctz wants to merge 2 commits intobriansmith:mainfrom
constant_time_conditional_memxor on GCC#2734ctz wants to merge 2 commits intobriansmith:mainfrom
Conversation
Owner
|
Good catch. Normally what we do in ring is simplify the code to match what is actually needed. In the case of the single caller of size_of(t_bytes) == 96, 96 % 32 == 0, so we could instead restrict I guess since the production use is with 96 bytes then we should be testing the 96 byte case specifically, at least. |
Owner
|
#2735 removes the offending code completely. |
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.
This fixes https://issues.chromium.org/issues/455606200 and tests the fix. If you drop the fix commit, the tests look like:
Which provides a demonstration of the upstream bug.