[Bug 1195118] some kernel modules cannot be loaded if secure boot is enabled
https://bugzilla.suse.com/show_bug.cgi?id=1195118 https://bugzilla.suse.com/show_bug.cgi?id=1195118#c22 Takashi Iwai <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo? | --- Comment #22 from Takashi Iwai <tiwai@suse.com> --- (In reply to Lukas Ocilka from comment #21)
(In reply to Takashi Iwai from comment #18)
Currently it's a simple %post script triggering from openSUSE-signkey-cert package. If we need an extra procedure after the root passwd setup in the installation step, it has to be executed manually?
Has this actually ever worked during installation?
I guess not, it seems that we haven't tested it full scenarios :-<
Has the feature been tested only on a running system where root obviously already has their hash in shadow? I'm trying to track it down by finding a working state and this one (15.3) to find the difference.
This must be broken from the beginning. Basically the feature is present only since Leap 15.3, and it's confirmed to broken, so...
The reason why I mentioned 15.4 is that we were changing some internal logic recently, but that would not change already release products.
Would 15.4 set up the root passwd before package installation? If so, the fix would be needed only for Leap 15.3 (for next possible quarterly update).
As far as I can see, this is actually a new thing in 15.3: https://build.opensuse.org/package/view_file/openSUSE:Leap:15.3/openSUSE- signkey-cert/openSUSE-signkey-cert.changes?expand=1
Right. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@suse.com