20251226-fixes #9589
Open
20251226-fixes #9589
+51
−36
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
…for !FORCE_FAILURE_RDSEED and !ENTROPY_MEMUSE_FORCE_FAILURE to follow the /dev/urandom fallback method.
…e callbacks and stdrng first before checking refcnt.
This comment was marked as spam.
This comment was marked as spam.
Contributor
Author
|
retest this please |
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.
wolfcrypt/benchmark/benchmark.c: smallstack refactor ofbench_mlkem_encap()wolfcrypt/src/random.c: inwc_GenerateSeed(), move the gate closures for !FORCE_FAILURE_RDSEEDand !ENTROPY_MEMUSE_FORCE_FAILUREto follow the/dev/urandomfallback method.linuxkm/lkcapi_sha_glue.c: inwc_linuxkm_drbg_startup(), deinstall the callbacks and default rngstdrngfirst before checking refcnt.wolfcrypt/src/aes.c: fixclang-diagnostic-unreachable-codeinAesSetKey_C().tested with
wolfssl-multi-test.sh ... '.*linuxkm.*' '.*insmod.*'(note that these fixes followed from expanded analytic test coverage around
--enable-linuxkm-defaultsand the FIPS v5-linuxkm and v6-linuxkm branches.)