You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add workaround for buggy AMI firmwares where appending to KEK fails
* Multiple user reports, as well as our own testing, seems to indicate that some
old-ish AMI UEFI firmwares on the likes of Lenovo, ASUS, Dell, MSI and HP, will
produce an error (EFI_INVALID_PARAMETER) when trying to append to the KEK Secure
Boot variables, if a KEK variable has already been set.
* This means that, on the affected machines, when we try to add the CA 2011 and
CA 2023 MS KEKs, as two separate SetVariable() operations, the second operation
fails (and this is regardless of what KEK we add first, or whether we generate
the ESL internally from the cert, or apply an externally generated ESL, which
hints that this is *not* an issue that is internal to Mosby, even more so as we
also see a similar issue with efitools' KeyTool).
* To work around this, we now merge the KEKs into a single, multi-entry ESL, before
applying it in a single SetVariable() operation (which is facilitated by the fact
that you can simply concatenate ESLs together to obtain an ESL array that UEFI
happily processes as multiple entries).
* Closes#14.
0 commit comments