diff options
| author | Serge Hallyn <serge@hallyn.com> | 2021-07-14 08:01:48 -0500 |
|---|---|---|
| committer | Peter Jones <pjones@redhat.com> | 2021-07-15 18:55:56 -0400 |
| commit | 0f40cb0d08798ed7557887958b382a42253c715d (patch) | |
| tree | 9e93f145a32e193dc8a91b92e67bd0a499f4bb98 | |
| parent | 9a8a6cdb5e862648ee663eee6124bed05208639a (diff) | |
| download | efi-boot-shim-0f40cb0d08798ed7557887958b382a42253c715d.tar.gz efi-boot-shim-0f40cb0d08798ed7557887958b382a42253c715d.zip | |
SBAT.md: fix "will should"
Use the stronger "will" rather than "will should". I'm not sure based on
what's there, but suspect "must" would be appropriate instead?
Signed-off-by: Serge Hallyn <serge@hallyn.com>
| -rw-r--r-- | SBAT.md | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -310,7 +310,7 @@ compromise. The initial SBAT implementation will add SBAT metadata to Shim and GRUB and enforce SBAT on all components labeled with it. Until a component (e.g. the Linux kernel) gains SBAT metadata it can not be revoked via SBAT, but only by -revoking the keys signing that component. These keys will should live in +revoking the keys signing that component. These keys will live in separate, product-specific signed PE files that contain **only** the certificate and SBAT metadata for the key files. These key files can then be revoked via SBAT in order to invalidate and replace a specific key. While |