[Bug 1094015] New: shim key management is shown at boot after every kernel upgrade (secure boot disabled)
http://bugzilla.opensuse.org/show_bug.cgi?id=1094015 Bug ID: 1094015 Summary: shim key management is shown at boot after every kernel upgrade (secure boot disabled) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: jsrain@suse.com Reporter: lbeltrame@kde.org QA Contact: jsrain@suse.com Found By: --- Blocker: --- As the summary states, with every kernel upgrade, the subsequent reboot shows the shim key management interface ("MOK Key Management"). This has been seen on three different machines: 1. Thinkpad T470 2. Dell Precision 3620 3. Self-assembled machine with a Z77 Intel chipset (ASUS) and its latest UEFI BIOS In all cases, secure boot was explicitly disabled, so there would be no need for it. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1094015 Jiri Srain <jsrain@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|jsrain@suse.com |glin@suse.com -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1094015 http://bugzilla.opensuse.org/show_bug.cgi?id=1094015#c1 --- Comment #1 from Gary Ching-Pang Lin <glin@suse.com> --- To simplify the boot path, we always boot from shim.efi no matter whether Secure Boot is enabled or not. The kernel postinstall script always invokes "mokutil --import <signkey> --root-pw" and openSUSE Signkey is different from the key (openSUSE CA) embedded in shim, so MokManager shows. It's harmless and can be ignored anyway. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1094015 http://bugzilla.opensuse.org/show_bug.cgi?id=1094015#c2 Linus Kardell <linus.kardell@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |linus.kardell@gmail.com --- Comment #2 from Linus Kardell <linus.kardell@gmail.com> --- It does however add another 10 seconds to the boot time after every update, and there seems to be no way to skip it, so it would be preferable if the screen wasn't shown. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1094015 http://bugzilla.opensuse.org/show_bug.cgi?id=1094015#c3 --- Comment #3 from Gary Ching-Pang Lin <glin@suse.com> --- There is a new argument, --timeout, for mokutil to set up the timeout of the screen, and the upcoming shim/MokManager supports that option. Once the shim update is applied, the timeout screen can be disabled with "mokutil --timeout 0". -- You are receiving this mail because: You are on the CC list for the bug.
participants (2)
-
bugzilla_noreply＠novell.com -
bugzilla_noreply＠suse.com