Remove jent_read_entropy_safe usage from AWS-LC (fips-2022-11-02)#2107
Merged
smittals2 merged 5 commits intoaws:fips-2022-11-02from Jan 15, 2025
Merged
Remove jent_read_entropy_safe usage from AWS-LC (fips-2022-11-02)#2107smittals2 merged 5 commits intoaws:fips-2022-11-02from
smittals2 merged 5 commits intoaws:fips-2022-11-02from
Conversation
smittals2
changed the title
andrewhop
previously approved these changes
Jan 13, 2025
skmcgrail
previously approved these changes
Jan 13, 2025
smittals2
changed the title
andrewhop
approved these changes
Jan 14, 2025
skmcgrail
approved these changes
Jan 14, 2025
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
3 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.
Issues:
P186365975Description of changes:
These changes remove any usage of jent_read_entropy_safe function from AWS-LC. This function has an implementation vulnerability described here.
jent_read_entropy_safe is now unused in our codebase, however, it is still present in the Jitter code. These changes are outside the FIPS boundary and do not impact the FIPS integrity hash.
Call-outs:
Point out areas that need special attention or support during the review process. Discuss architecture or design changes.
Testing:
How is this change tested (unit tests, fuzz tests, etc.)? Are there any testing steps to be verified by the reviewer?
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license and the ISC license.