** Description changed: + [Impact] + Upstream linux kernel now supports configuring built-in revoked certificates for the .blacklist keyring. Add support in our kernel configuration to have built-in certificates. Revoke UEFI amd64 & arm64 2012 signing certificate. Under UEFI Secureboot with lockdown, shim may attempt to pass revoked certificates to the kernel and depending on how good EFI firmware is this may or may not succeed. By having these built-in, it will be prohibited to kexec file_load older kernels that were signed with now revoked certificates. + + + [Test Plan] + + * Boot kernel directly, or just with grub, and without shim + + * Check that + + $ sudo keyctl list %:.blacklist + + Contains assymetric 2012 key. + + [Where problems could occur] + + * Derivative and per-arch kernels may need to revoke different keys, + thus this should be evaluated on per arch & flavour basis as to which + keys to revoke. + + [Other Info] + + * In theory, this only needs to be revoked on amd64 and arm64, but empty revocation list is not allowed by the kernel configury, thus at the moment revoking 2012 UEFI cert for all architectures.
** Description changed: [Impact] Upstream linux kernel now supports configuring built-in revoked certificates for the .blacklist keyring. - Add support in our kernel configuration to have built-in certificates. + Add support in our kernel configuration to have built-in revoked + certificates. Revoke UEFI amd64 & arm64 2012 signing certificate. - Under UEFI Secureboot with lockdown, shim may attempt to pass revoked - certificates to the kernel and depending on how good EFI firmware is - this may or may not succeed. + Under UEFI Secureboot with lockdown, shim may attempt to communicate + revoked certificates to the kernel and depending on how good EFI + firmware is, this may or may not succeed. By having these built-in, it will be prohibited to kexec file_load older - kernels that were signed with now revoked certificates. - + kernels that were signed with now revoked certificates, however one + boots. [Test Plan] - * Boot kernel directly, or just with grub, and without shim + * Boot kernel directly, or just with grub, and without shim - * Check that + * Check that $ sudo keyctl list %:.blacklist Contains assymetric 2012 key. [Where problems could occur] - * Derivative and per-arch kernels may need to revoke different keys, + * Derivative and per-arch kernels may need to revoke different keys, thus this should be evaluated on per arch & flavour basis as to which keys to revoke. [Other Info] - - * In theory, this only needs to be revoked on amd64 and arm64, but empty revocation list is not allowed by the kernel configury, thus at the moment revoking 2012 UEFI cert for all architectures. + + * In theory, this only needs to be revoked on amd64 and arm64, but + empty revocation list is not allowed by the kernel configury, thus at + the moment revoking 2012 UEFI cert for all architectures. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1932029 Title: Support builtin revoked certificates Status in linux package in Ubuntu: New Bug description: [Impact] Upstream linux kernel now supports configuring built-in revoked certificates for the .blacklist keyring. Add support in our kernel configuration to have built-in revoked certificates. Revoke UEFI amd64 & arm64 2012 signing certificate. Under UEFI Secureboot with lockdown, shim may attempt to communicate revoked certificates to the kernel and depending on how good EFI firmware is, this may or may not succeed. By having these built-in, it will be prohibited to kexec file_load older kernels that were signed with now revoked certificates, however one boots. [Test Plan] * Boot kernel directly, or just with grub, and without shim * Check that $ sudo keyctl list %:.blacklist Contains assymetric 2012 key. [Where problems could occur] * Derivative and per-arch kernels may need to revoke different keys, thus this should be evaluated on per arch & flavour basis as to which keys to revoke. [Other Info] * In theory, this only needs to be revoked on amd64 and arm64, but empty revocation list is not allowed by the kernel configury, thus at the moment revoking 2012 UEFI cert for all architectures. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1932029/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
