@costamagnagianfranco From my understanding, all new modules will now have to be signed since the signature enforcement was activated in the kernel. So, the dkms system would have to generate a local system key, add this local key to the trusted keystore and would have to sign all third-party-modules in the future.
I removed and purged the virtualbox-dkms (which obviously wouldn't fix the problem), but am unsure on how to proceed from here. Would I have to build and sign the kernel module myself - and do so for every new kernel installation? Or will there be a convenience package from you doing that?
@costamagnagian franco From my understanding, all new modules will now have to be signed since the signature enforcement was activated in the kernel. So, the dkms system would have to generate a local system key, add this local key to the trusted keystore and would have to sign all third-party-modules in the future.
I removed and purged the virtualbox-dkms (which obviously wouldn't fix the problem), but am unsure on how to proceed from here. Would I have to build and sign the kernel module myself - and do so for every new kernel installation? Or will there be a convenience package from you doing that?