summaryrefslogtreecommitdiffstats
path: root/wiki/src
diff options
context:
space:
mode:
authorintrigeri <intrigeri@boum.org>2019-04-11 07:53:00 +0000
committerintrigeri <intrigeri@boum.org>2019-04-11 07:54:42 +0000
commite008e3be304eee9c6e1acb7fa04789bf1cef4eee (patch)
tree71a4e141ae6bf4129805034f17fdd7465827eb54 /wiki/src
parente22fd9efdc71bd32f0d8d4b0356ef7c3784fc66b (diff)
Add more resources about automated testing of Secure Boot.
Diffstat (limited to 'wiki/src')
-rw-r--r--wiki/src/blueprint/UEFI_Secure_boot.mdwn11
1 files changed, 11 insertions, 0 deletions
diff --git a/wiki/src/blueprint/UEFI_Secure_boot.mdwn b/wiki/src/blueprint/UEFI_Secure_boot.mdwn
index 1b246f3..50337fb 100644
--- a/wiki/src/blueprint/UEFI_Secure_boot.mdwn
+++ b/wiki/src/blueprint/UEFI_Secure_boot.mdwn
@@ -52,5 +52,16 @@ Resources
by Greg Kroah-Hartman
* Linux Foundation's
[Making UEFI Secure Boot Work With Open Platforms](http://linuxfoundation.org/publications/making-uefi-secure-boot-work-with-open-platforms)
+
+Automated testing
+=================
+
+* The hard(est) part seems to be about how to enroll the signing keys
+ into the nvram file. One option is to use `EnrollDefaultKeys.efi`
+ from OVMF.
* [Automating Secure Boot Testing](https://www.youtube.com/watch?v=qtyRR-KbXYQ):
how Red Hat does CI for Secure Boot (FOSDEM 2018)
+* <https://wiki.ubuntu.com/UEFI/SecureBoot/Testing>
+* <https://en.opensuse.org/openSUSE:UEFI_Secure_boot_using_qemu-kvm>
+* <https://fedoraproject.org/wiki/Using_UEFI_with_QEMU#Testing_Secureboot_in_a_VM>
+* <https://github.com/puiterwijk/qemu-ovmf-secureboot>