Does the proposed kernel disable signature verification by default? If
not, the bug will persist.
Moreover, this enforcement was by design.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1574300
Title
@ejohn Yes, I did the same too.
output of
> sudo mokutil --list-enrolled
lists the key I created.
And also,
> strings driver.ko
has a `~Module signature appended~` at the end, with my signature name.
Inference is that I have successfully enrolled the key which I created in
mokutils.
The mo
I used the kernel-source/scripts/sign-file utility to sign the driver,
but still I get the same error. How to find out if a module is signed or
not?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/157430
Thanks for the info. This is not a bug,
"Since Ubuntu kernel 4.4.0-20 the EFI_SECURE_BOOT_SIG_ENFORCE kernel
config has been enabled. That prevents from loading unsigned third party
modules if UEFI Secure Boot is enabled.
Since Ubuntu kernel build 4.4.0-21.37 this can be fixed by running
sudo ap
But if something works in 15.10 and breaks in 16.04 LTS, then it can be
considered a bug :)
it does not seem a bug, but a policy; see
https://answers.launchpad.net/ubuntu/+question/292158
https://www.virtualbox.org/ticket/11577#comment:2
to disable validation of modules (and maybe of kernel too
systemctl status virtualbox.service output
● virtualbox.service - LSB: VirtualBox Linux kernel module
Loaded: loaded (/etc/init.d/virtualbox; bad; vendor preset: enabled)
Active: failed (Result: exit-code) since Sun 2016-04-24 20:34:40 IST; 1min
1s ago
Docs: man:systemd-sysv-generator(
This is the apt-get install output
DKMS: install completed.
Setting up virtualbox (5.0.18-dfsg-2build1) ...
vboxweb.service is a disabled or a static unit, not starting it.
Job for virtualbox.service failed because the control process exited with error
code. See "systemctl status virtualbox.servi
Public bug reported:
http://askubuntu.com/q/760671
I upgrade from Ubuntu 15.10 to 16.04 and since then VirtualBox 5.0.18 isn't
starting my VMs anymore. It complains that 'vboxdrv' isn't loaded. So I try to
load it and get the following error:
$ sudo modprobe vboxdrv
modprobe: ERROR: could not
