summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJan Setje-Eilers <jan.setjeeilers@oracle.com>2024-12-23 10:04:05 -0800
committerPeter Jones <pjones@redhat.com>2025-02-05 09:10:35 -0500
commite886fb35ad02c3d1aadb974aec7ded3451ea557f (patch)
tree7b27d883d6c37f46d707cf558c64127c5ed4fe92
parent5ae408aede0a410f28de92a5fdc5ce406f2c4515 (diff)
downloadefi-boot-shim-e886fb35ad02c3d1aadb974aec7ded3451ea557f.tar.gz
efi-boot-shim-e886fb35ad02c3d1aadb974aec7ded3451ea557f.zip
SbatLevel_Variable.txt: clarify where and how revocation data is tracked
Comments to clarify that revocations should only be recorded in SbatLevel_Variable.txt and not in any other header files. Signed-off-by: Jan Setje-Eilers <Jan.SetjeEilers@oracle.com>
-rw-r--r--SbatLevel_Variable.txt15
1 files changed, 12 insertions, 3 deletions
diff --git a/SbatLevel_Variable.txt b/SbatLevel_Variable.txt
index 0c61f306..407f1337 100644
--- a/SbatLevel_Variable.txt
+++ b/SbatLevel_Variable.txt
@@ -1,6 +1,15 @@
-In order to apply SBAT based revocations on systems that will never
-run shim, code running in boot services context needs to set the
-following variable:
+This file is the single source for SbatLevel revocations the format
+follows the variable payload and should not have any leading or
+trailing whitespace on the same line.
+
+Short descriptions of the revocations as well as CVE assignments (when
+available) should be provided when an entry is added.
+
+On systems that run shim, shim will manage these revocations. Sytems
+that never run shim, primarily Windows, but this applies to any OS
+that supports UEFI Secure Boot under the UEFI CA without shim can
+apply SBAT based revocations by setting the following variable
+from code running in boot services context.
Name: SbatLevel
Attributes: (EFI_VARIABLE_NON_VOLATILE | EFI_VARIABLE_BOOTSERVICE_ACCESS)