If you need more information fell free to ask. That module would be correctly loaded because that key had already been imported by me using MOK.

just in case someone takes control of my machine, he/she could signs a malicious module using akmod. The akmod private key is not password protected, so. The only thing that worries me is about the security perspective. But, I can surely tell that the already signed modules by akmod work correctly. I've never tested a VirtualBox upgrade process yet, because I've just installed the latest VirtualBox version. class of kernel or video driver bug is a blank or black screen on boot. So, signing modules everytime you upgrade Virtualbox it won't be needed anymore. Even the installation of the Anniversary update did not correct this issue. ĭoing that, my expectation is that everytime VirtualBox will be updated, the modules will be automatically loaded. I was able to discover where the akmod keypair was stored and then I imported that public key in MOK. It was easily discoverable using modinfo. I found this post because I've just updated to Fedora 36 and looked for a solution for the same issue.Įverything you found out is true and I thank you a lot for everything, but I wanted tell you I've found a clever shortcut.ĭuring the issue investigation process, I found out the *.ko.xz modules were already signed by akmod. Note that this script probably is meant for another rpmfusion package maybe? The official package does not provide compressed modules. This deals with compressed kernel modules if found (fedora36) #!/bin/sh readonly hash_algo= 'sha256 ' readonly key= '/root/module-signing/MOK.priv ' readonly x509= '/root/module-signing/MOK.der ' readonly name= ' $(basename $0 ) ' readonly esc= '\e ' readonly reset= ' $ ' fi done

Virtualbox linux wihtout kernel drivers