Repository navigation
Allow the test-only weak entropy fallback in the Zephyr QEMU CI build - #671
Merged
Merged
Conversation
aidangarske
approved these changes
Nov 10, 2026
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.
wolfSSL now refuses to build its Zephyr seed source when the devicetree has no chosen entropy device, unless
WOLFSSL_ACCEPT_WEAK_ENTROPYis defined (wolfSSL/wolfssl#12065). Theqemu_x86board used by the Zephyr job has none, so the job fails inwc_GenerateSeed().The job now prepends that define to wolfSSL's
zephyr/user_settings.hafterwest update, the same CI-only opt-in wolfSSL's own Zephyr workflow uses. The samples and theirprj.confare unchanged, so builds outside CI still need a real entropy source.