Opened 3 years ago
Closed 10 months ago
#20465 closed defect (obsolete)
Failure to load signed modules on UEFI secure boot system
Reported by: | Tomek | Owned by: | |
---|---|---|---|
Component: | installer | Version: | VirtualBox 6.1.24 |
Keywords: | Cc: | ||
Guest type: | all | Host type: | Linux |
Description
As in title really. VirtualBox scripts build the modules, put them in right place but they (rightfully) cannot be loaded.
So I sign them.
And the story repeats - /usr/lib/virtualbox/vboxdrv.sh scripts doesn't recognize the drivers as valid ones, rebuilds them (trashing the signature I've just made) and the story repeats.
The problem probably is in line 330 in function module_available():
[ "$mod_dir" != "misc" ] return
which likely should be:
[ "$mod_dir" = "misc" ] return
Note:
See TracTickets
for help on using tickets.
Hi Tomek,
There were number of changes in this area since 6.1.24. Some distributions do not provide necessary tools which
rcvboxdrv
andrcvboxadd
scripts need to verify module signatures. If signature cannot be verified, scripts will attempt to rebuild modules. This might be a reason for the issue you are observing. Starting from VirtualBox 7.0.8, there is a possibility to bypass modules signature verification and let scripts to try to load modules as-is. In order to do that the following line needs to be added into /etc/vbox/vbox.cfg (for host package) and/or /etc/virtualbox-guest-additions.conf (for Guest Additions):VirtualBox 6.1.x does not have this tweak. Closing as obsolete.