fix: Temporarily allow WARNING as well as AFFIRMING status in EAR submodules #7
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.
Small tweak to the EAR eval logic that gates whether the wrapped secret is released to the caller.
The algorithm remains ultra-simple and neutral with respect to AR submodule composition. The previous algorithm required an
affirming
status from every submodule. The new one allowswarning
as well. This isn't exactly desirable, but it keeps the key broker working while we handle some deeper issues around CCA realm/workload attestation, which was recently added to Veraison.Signed-off-by: Paul Howard paul.howard@arm.com