FEDORA-2022-e4be550a47 — bugfix update for mokutil

stable

mokutil-0.6.0-3.fc36

FEDORA-2022-e4be550a47 created by pjones 3 years ago for Fedora 36

Fixes a command line handling bug.

How to install

Updates may require up to 24 hours to propagate to mirrors. If the following command doesn't work, please retry later:

sudo dnf upgrade --refresh --advisory=FEDORA-2022-e4be550a47

This update has been submitted for testing by pjones.

3 years ago

This update's test gating status has been changed to 'ignored'.

3 years ago

vwbusguy commented & provided feedback 3 years ago

$ sudo mokutil -s Aborted

$ sudo mokutil --sb-state mokutil: unrecognized option '--sb-state' Usage: mokutil OPTIONS [ARGS...] ...

$ rpm -q mokutil mokutil-0.6.0-2.fc36.x86_64

BZ#2087066 mokutil -s aborts without error message

vwbusguy commented & provided feedback 3 years ago

I'm guessing it's related to the recent usage patch. Seems to work fine compiled from scratch against upstream.

src]$ sudo ./mokutil --sb-state
SecureBoot disabled

src]$ sudo ./mokutil -s
Usage:
  mokutil OPTIONS [ARGS...]

Options:
  --help                Show help
  --list-enrolled           List the enrolled keys

vwbusguy commented & provided feedback 3 years ago

So, after compiling and running mokutil from upstream source and running it, the Fedora RPM command also oddly started working. I did not sudo make install and rpm -V mokutil returns empty. I also removed the two build deps I installed (efivar-devel keyutils-libs-devel) and it still works.

In order to rule out a random fluke on my laptop, I ran sudo mokutil --bs-state on another f36 laptop and it returned the original error and usage instead of the secureboot status. It working after compiling it locally as a non-root user without make install makes no sense to me, but I can reproduce it on multiple f36 machines of different brands.

This update has been pushed to testing.

3 years ago

geraldosimiao commented & provided feedback 3 years ago

karma

Generally funcional yes, but the coredump bug still there:

rpm -qa|grep mokutil ==> mokutil-0.6.0-2.fc36.x86_64
mokutil --sb-state ==> SecureBoot disabled
mokutil -s ==> Abortado (imagem do núcleo gravada)

coredumpctl info
       PID: 6979 (mokutil)
       UID: 1000 (geraldo)
       GID: 1000 (geraldo)
    Signal: 6 (ABRT)
 Timestamp: Wed 2022-05-25 15:17:48 -03 (56s ago)
Command Line: mokutil -s
Executable: /usr/bin/mokutil
Control Group: /user.slice/user-1000.slice/user@1000.service/app.slice/app-org.kde.konsole-cc4451fdcc194b2e98e5b50fe77f9a23.scope
      Unit: user@1000.service
 User Unit: app-org.kde.konsole-cc4451fdcc194b2e98e5b50fe77f9a23.scope
     Slice: user-1000.slice
 Owner UID: 1000 (geraldo)
         Storage: /var/lib/systemd/coredump/core.mokutil.1000.613f9a483d494871ad63650de27d7ad0.6979.1653502668000000.zst (present)
 Disk Size: 78.9K
   Message: Process 6979 (mokutil) of user 1000 dumped core.

BZ#2087066 mokutil -s aborts without error message

pjones edited this update.

New build(s):