Package: virtualbox-dkms Version: 6.0.10-dfsg-5 Severity: important Dear Maintainer,
Recent Debian Linux kernels have started to enfore module signature checking when the system is booted with UEFI Secure Boot enabled. This renders DKMS modules non-loadable, because they do not get signed with an enrolled key by default. According to https://www.virtualbox.org/ticket/11577 , the issue was supposed to be fixed in Debian 10+, but this is not the case. Any attempts to create and enroll a Machine Owner Key (MOK) and sign with that have also failed, it is still impossible to load the built DKMS modules. Please provide some way to automatically sign DKMS modules, or at least warn users with a proper message that VirtualBox does not work well with Secure Boot enabled. Thanks! -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (600, 'testing'), (100, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.2.0-2-amd64 (SMP w/8 CPU cores) Kernel taint flags: 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 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages virtualbox-dkms depends on: ii dkms 2.7.1-2 Versions of packages virtualbox-dkms recommends: ii virtualbox 6.0.10-dfsg-5 virtualbox-dkms suggests no packages. -- no debconf information
