Skip to content

Commit bd893fe

Browse files
committed
redhat: conflict with unsupported shim on x86/aarch64
JIRA: https://issues.redhat.com/browse/RHEL-126425 Upstream Status: RHEL only The kernel has recently switched to using 800-series keys for SecureBoot and this requires shim to have the corresponding CA certificate. The first version which had it was 15.8-1 so in case the new kernel is installed with an older shim, 'Security violation' error is going to prevent booting when SecureBoot=on. Prevent such broken combos by adding an explicit conflict. The problem can easily be observed on x86 by upgrading the kernel to a recent version on an old (RHEL9.2 and below) system. Aarch64 systems are only theoretically affected as SecureBoot was not supported by these old releases. Note: UKI is not affected by the issue as it still uses 504 key. Signed-off-by: Vitaly Kuznetsov <vkuznets@redhat.com>
1 parent 88031a6 commit bd893fe

File tree

1 file changed

+3
-0
lines changed

1 file changed

+3
-0
lines changed

redhat/kernel.spec.template

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -975,6 +975,9 @@ Recommends: linux-firmware\
975975
Requires(preun): systemd >= 200\
976976
Conflicts: xfsprogs < 4.3.0-1\
977977
Conflicts: xorg-x11-drv-vmmouse < 13.0.99\
978+
%ifarch x86_64 aarch64\
979+
Conflicts: shim < 15.8-1\
980+
%endif\
978981
%{expand:%%{?kernel%{?1:_%{1}}_conflicts:Conflicts: %%{kernel%{?1:_%{1}}_conflicts}}}\
979982
%{expand:%%{?kernel%{?1:_%{1}}_obsoletes:Obsoletes: %%{kernel%{?1:_%{1}}_obsoletes}}}\
980983
%{expand:%%{?kernel%{?1:_%{1}}_provides:Provides: %%{kernel%{?1:_%{1}}_provides}}}\

0 commit comments

Comments
 (0)