Rename "previous" revocations to "automatic"

When the term previous was introduced for revocations to be automatically applied there was a hope that everytime a new revocation was built into shim, the previous revocation could be applied automatically. Further experience has shown the real world to be more complex than that. The automatic payload will realistically contain a set of revocations governed by both the cadence at which a distro's customer base updates as well as the severity of the issue being revoked. This is not a functional change. Signed-off-by: Jan Setje-Eilers <Jan.SetjeEilers@oracle.com>
rhboot · Dec 15, 2023 · 9f64cca · 9f64cca
1 parent e9d2901
commit 9f64cca
Show file tree

Hide file tree

Showing 3 changed files with 0 additions and 0 deletions.
diff --git a/data/SkuSiPolicy_Version_previous.bin → data/SkuSiPolicy_Version_automatic.bin b/data/SkuSiPolicy_Version_previous.bin → data/SkuSiPolicy_Version_automatic.bin
diff --git a/data/SkuSiPolicy_previous.bin → data/SkuSiPolicy_automatic.bin b/data/SkuSiPolicy_previous.bin → data/SkuSiPolicy_automatic.bin
diff --git a/data/sbat_level_previous.csv → data/sbat_level_automatic.csv b/data/sbat_level_previous.csv → data/sbat_level_automatic.csv