summaryrefslogtreecommitdiffstats
path: root/wiki/src
diff options
context:
space:
mode:
author127.0.0.1 <127.0.0.1@web>2019-04-12 19:22:10 +0000
committerIkiWiki <ikiwiki.info>2019-04-12 19:22:10 +0000
commita121902c29da5bd3574f8d2b7cd66f55efe151dd (patch)
tree7d31e499d70409de140dea24b3f001f68367ad11 /wiki/src
parentf9dbebe97261bf85f38f9b037354db160d53d21d (diff)
This reverts commit e008e3be304eee9c6e1acb7fa04789bf1cef4eee
Diffstat (limited to 'wiki/src')
-rw-r--r--wiki/src/blueprint/UEFI_Secure_boot.mdwn11
1 files changed, 0 insertions, 11 deletions
diff --git a/wiki/src/blueprint/UEFI_Secure_boot.mdwn b/wiki/src/blueprint/UEFI_Secure_boot.mdwn
index 50337fb..1b246f3 100644
--- a/wiki/src/blueprint/UEFI_Secure_boot.mdwn
+++ b/wiki/src/blueprint/UEFI_Secure_boot.mdwn
@@ -52,16 +52,5 @@ 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>