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!

Some scripts that might help:

- https://github.com/ivan-californias/vbox-sign-modules
- https://github.com/Majal/maj-scripts/blob/master/vboxsign

Or better a more generic solution of signing all DKMS modules:

https://gist.github.com/dop3j0e/2a9e2dddca982c4f679552fc1ebb18df

New versions of DKMS have a `SIGN_TOOL=` feature. Please have a look,
see if that looks alright, and give feedback to the DKMS developers:

* https://github.com/dell/dkms/issues/72
* https://github.com/dell/dkms/pull/87
passed to the signing tool. The first argument is the target kernel
version, the second is the module file path. If the tool exits with a
non-zero value, the build will be aborted.


Kind regards,
Patrick