Cannot load modules with 16.04 on non uefi boards with normal bios and 32 bit
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux-lts-xenial (Ubuntu) |
Confirmed
|
Medium
|
Unassigned |
Bug Description
The secure boot option is supposed to work only for 64Bit and mainboard which support uefi. However, I experienced that a signature is mandatory also for non uefi boards with normal bios and 32 bit. My system is Ubuntu 16.04/32Bits and 4.4.0-59-generic kernel. I use the standard kernel.
1) If I build a module like I always did on Ubuntu 10.4 and 14.04 but now on 16.04 and try to load it, I get the following error in `dmesg | tail`: `module verification failed: signature and/or required key missing - tainting kernel`.
2) I create a key pair (`/usr/
00004e60 7e 4d 6f 64 75 6c 65 20 73 69 67 6e 61 74 75 72 |~Module signatur|
00004e70 65 20 61 70 70 65 6e 64 65 64 7e 0a |e appended~.|
00004e7c
And tried to load the keys with ` sudo mokutil --import MOK.der ` but I get the error:
EFI variables are not supported on this system
3) I tried to disable the signature validation
# sudo mokutil --disable-
EFI variables are not supported on this system
4) I added in grub `noefi` and ` acpi_enforce_
5) IU was looking for the private key of the kernel in order to sign my generated key with the kernel key. If I would found the private key, it would have completely useless to introduce signatures to Ubuntu J
6 Try) Suggestions by Rod Smith to install the MokManager.efi were not successful because it requires an uefi motherboard.
Other tries are suggested by Rod Smith here (http://
Could you please fix the bug? Please let me know I you need more information.
information type: | Private Security → Public |
description: | updated |
Changed in linux-lts-xenial (Ubuntu): | |
importance: | Undecided → Medium |
Hello :)
I'm not sure how the report ended up here, but this issue doesn't seem related to Widelands. I've therefore taken the liberty of moving it to the Ubuntu bug tracker. I'm not familiar with the details here, so I don't know whether this would fall in under the kernel package, grub or possibly some third option.