Add UEFI Secure Boot with unsigned kernel case (New) #1440
Merged
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
Currently, for secure boot coverage, Checkbox only has miscellanea/secure_boot_mode to check secure boot is enabled from System level.
However, based on the responsibility of publishing image, Canonical is responsible for the signed shim, grub and kernel. Therefore, I add a manual case to replace signed kernel with unsigned kernel to prove the function of UEFI Secure Boot is working as expected.
This is raised from Boashan Project but the testing method is generic. So Canonical QA can follow the step to verify UEFI Secure Boot feature if a project supports UEFI firmware on Classic image.
Resolved issues
Documentation
Tests