summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
author127.0.0.1 <127.0.0.1@web>2019-04-21 02:29:54 +0000
committerIkiWiki <ikiwiki.info>2019-04-21 02:29:54 +0000
commit0148776b93cc98ff32a1c7ca4fb7a0a0805ffba1 (patch)
tree2c589bab250dbfcf18f74525bfe658a57b8122bc
parent2fff8fdd7af758d4e044db802c5f3026fda53743 (diff)
This reverts commit a797287d907603863874b461be5054d8af53be87
-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>