[Git-commits] [grml/grml-autoconfig] a08b34: running_under_secureboot: update for efivarfs + ne...

[Michael Prokop]

  Branch: refs/heads/master
  Home:   https://github.com/grml/grml-autoconfig
  Commit: a08b34912e982a01f7bf80bf35ae009af522b43a
      https://github.com/grml/grml-autoconfig/commit/a08b34912e982a01f7bf80bf35ae009af522b43a
  Author: Michael Prokop <mika at grml.org>
  Date:   2022-03-21 (Mon, 21 Mar 2022)

  Changed paths:
    M autoconfig.functions

  Log Message:
  -----------
  running_under_secureboot: update for efivarfs + new mokutil behavior

CONFIG_EFI_VARS is no longer available since
https://salsa.debian.org/kernel-team/linux/-/commit/20146398c4599147244ed3ffc54f38d07fb8dea3
(tagged initially as debian/5.10.1-1_exp1 + shipped with kernel package
5.10.1-1~exp1 and newer, incl. 5.10.0-12-amd64 as present in current
Debian/bullseye). Therefore the kernel module efivars is no longer
available on more recent Debian kernel systems, but efivarfs
needs to be used instead.

The behavior of mokutil also seems to have changed. On systems where
SecureBoot is available but not enabled, it outputs "SecureBoot
disabled", while no longer returning with an exit code other than 0.
On systems where Secure Boot isn't supported (e.g. in VirtualBox) it
reports "This system doesn't support Secure Boot" on stderr, with exit
code 255.

Verified with mokutil 0.3.0+1538710437.fb6250f-1

This work was funded by Grml-Forensic.


  Commit: af578f247f401edc1f56039a2528b397c6a467bb
      https://github.com/grml/grml-autoconfig/commit/af578f247f401edc1f56039a2528b397c6a467bb
  Author: Michael Prokop <mika at grml.org>
  Date:   2022-03-21 (Mon, 21 Mar 2022)

  Changed paths:
    M debian/changelog

  Log Message:
  -----------
  Release new version 0.20.2


Compare: https://github.com/grml/grml-autoconfig/compare/3e0630579b99...af578f247f40