Yes, it would be more user-friendly to disable secure boot instead of
asking a user to go through the process of importing a new key after
every kernel or driver upgrade. Therefore, I will modify my proposal a
bit and suggest that the menu to disable secure boot should have a new
option to add
/VBOX.der
$(modinfo -n vboxdrv)
On Sun, Jul 3, 2016 at 3:18 PM, Kaosu NA wrote:
> I do not see why the developers have chosen to prompt users to disable
> secure boot in order to install third-party drivers. While I understand
> that Canonical is unable to use their key to sign kerne
I do not see why the developers have chosen to prompt users to disable
secure boot in order to install third-party drivers. While I understand
that Canonical is unable to use their key to sign kernel modules generated
by DKMS, it would be trivial to generate, sign and import a key for select
third-
