Package: shim-signed Version: 1.44+15.8-1 Severity: minor When updating kernel modules on secure boot that don't work with it, apt shows this message that AIU comes from shim-signed: > Your system has UEFI Secure Boot enabled > > UEFI Secure Boot is not compatible with the use of third-party > drivers. To ensure that this change is being made [...] The user needs to take a decision whether to disable secureboot or to leave it on, but to make an *informed* decision, the user will need to know which those third-party drivers are. In my case, I think it was the v4l loopback, so I stuck with secureboot, but apt dialogues should preferably not invite guessing. I have no clue how that information is available at this point, but it would have helped me to see something like: > The third-party drivers that will be unavailable if secureboot statys > active are: > > - virtualbox-dkms > - v4l-loopback thanks for your consideration, and for maintaining this Christian -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.6.8-amd64 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: sysvinit (via /sbin/init) LSM: AppArmor: enabled Versions of packages shim-signed depends on: ii grub-efi-amd64-bin 2.12-2~deb13u1 ii grub2-common 2.12-2~deb13u1 ii shim-helpers-amd64-signed 1+15.8+1 ii shim-signed-common 1.44+15.8-1 shim-signed recommends no packages. shim-signed suggests no packages. -- no debconf information
Attachment:
signature.asc
Description: PGP signature