Fix for Compressed Keys with FIPS #8248
Merged
Conversation
This file contains 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
kaleb-himes
approved these changes
Dec 3, 2024
There was a problem hiding this comment.
Tested with modules v5.2.1, v5.2.3 and v6.0.0, good to go! Thanks @lealem47!
|
Jenkins Retest this please |
JacobBarthelmeh
approved these changes
Dec 4, 2024
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.
Description
The macro guard that was edited in this PR should have accounted for HAVE_FIPS_VERSION=5 as well as HAVE_FIPS_VERSION=2, since neither versions have the get length functionality available with compressed keys
Fixes zd#
Testing
wolfCrypt tests with
./configure --enable-fips=v5 CFLAGS=-DHAVE_COMP_KEYfails before this PRChecklist