Package: mokutil
Version: 0.2.0-1+b3
Severity: grave
Tags: patch
Justification: renders package unusable

Dear Maintainer,

*** Reporter, please consider answering these questions, where
appropriate ***

   * What led up to the situation?
     - Trying to test Secure Boot support, as in
https://wiki.debian.org/SecureBoot/Testing.
   * What exactly did you do (or not do) that was effective (or
     ineffective)?
     - Follow the guide until step 5.1 (which is the step where mokutil
     fails).
   * What was the outcome of this action?
     - After prompting for a password twice, mokutil fails with the
     following error message:
Failed to write MokAuth
Failed to unset MokNew
Failed to enroll new keys
   * What outcome did you expect instead?
     - mokutil does not fail.

*** End of the template - remove these template lines ***

The reason for the failure is that since some time ago, Linux started
creating EFI variables as immutable. Our old version of mokutil does
not care about this.
Thus, when mokutil attempts to write a second time (MokAuth) or unlink
(MokNew) a variable, the operation fails.



-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8),
LANGUAGE=de:fr:en_US (charmap=UTF-8) Shell: /bin/sh linked
to /usr/bin/dash Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages mokutil depends on:
ii  libc6      2.28-8
ii  libssl1.1  1.1.1b-1

mokutil recommends no packages.

mokutil suggests no packages.

-- no debconf information

Attachment: immutable-variables
Description: Binary data

Reply via email to