A simple password is good enough, as it is only for temporary use. This is a two step process where the key is first imported, and then later must be enrolled when the machine is booted the next time. Use the MOK (“Machine Owner Key”) utility to import the public key so that it can be trusted by the system.# openssl req -new -x509 -newkey rsa:2048 -keyout MOK.priv -outform DER -out MOK.der -nodes -days 36500 -subj "/CN=YOUR_NAME/"
I chose to use the root account and the directory /root/module-signing/ to store all things related to signing kernel modules. Create a personal public/private RSA key pair which will be used to sign kernel modules.If the installation detects that Secure Boot is enabled, you will be presented with the issue at hand and given the option to disable Secure Boot. Steps to make it work, specifically for Ubuntu/Debian *Ubuntu 16.04 on a Dell Latitude E7440 with BIOS A18, and with a dual boot Windows 10 installation.Ĭredit goes to the primary source of information I used to resolve this problem, which applies specifically to Fedora/Redhat: I could do that, but then I would see an annoying “Booting in insecure mode” message every time the machine starts, and also the dual boot Windows 10 installation I have would not function. Ubuntu does not sign the third party vbox* kernel modules, but rather gives the user the option to disable Secure Boot upon installation of the virtualbox package. The problem is the requirement that all kernel modules must be signed by a key trusted by the UEFI system, otherwise loading will fail. Here are the steps I did to enable VirtualBox to work properly in Ubuntu with UEFI Secure Boot fully enabled*.
0 kommentar(er)
