4 ms·
"Signing the kernel isn't enough. Signed Linux kernels must refuse to load any unsigned kernel modules. Virtualbox on Linux? Dead. Nvidia binary driver on Linux
by comex 15y ago
"Signing the kernel isn't enough. Signed Linux kernels must refuse to load any unsigned kernel modules. Virtualbox on Linux? Dead. Nvidia binary driver on Linux? Dead. All out of tree kernel modules? Utterly, utterly dead. Building an updated driver locally? Not going to happen. That's going to make some people fairly unhappy."
Making secure boot meaningful on Linux would be a big project - you'd also have to sign most of the stuff in userland. But if it were done, it would be done by the distro, which could easily enough sign the kernel module in its VirtualBox package and whatever else users might want to load into the kernel. Since this would presumably be optional (there would be an alternate signed bootloader that loaded an unsigned kernel for developers and power users), the GPL3 would be satisfied; and the end result is a system that's significantly harder to attack. I don't know if that's worth the effort, considering the lack of actual malware for Linux, but as long as the key is installed along with the OS, it's hardly an impossibility.
- mjg59 15y agoIf you provide binary Virtualbox drivers, sure. I'm not aware of any distributions that do that - they provide source instead. And signing external drivers requires auditing them to make sure that there's no way they can be exploited to execute arbitrary code, because if they can then you've just signed a malware loader and Microsoft (if they're serious about secure boot being about security) blacklist your key.
- lordlicorice 15y agoI don't think that makes sense since most Linux users don't even normally have a C compiler (let alone kernel headers) installed on their systems...
- mjg59 15y agoMost Linux users don't normally use any out of tree drivers. https://help.ubuntu.com/community/VirtualBox/Installation https://help.ubuntu.com/community/VirtualBox/Installation indicates that Virtualbox is shipping via DKMS, which is infrastructure for automatically rebuilding the Virtualbox code every time the kernel is updated.
- lloeki 15y ago$ pacman -Ql virtualbox-modules virtualbox-modules /lib/ virtualbox-modules /lib/modules/ virtualbox-modules /lib/modules/extramodules-3.1-ARCH/ virtualbox-modules /lib/modules/extramodules-3.1-ARCH/vboxdrv.ko.gz virtualbox-modules /lib/modules/extramodules-3.1-ARCH/vboxnetadp.ko.gz virtualbox-modules /lib/modules/extramodules-3.1-ARCH/vboxnetflt.ko.gz virtualbox-modules /lib/modules/extramodules-3.1-ARCH/vboxpci.ko.gz Same for extra/nvidia, while extra/xf86-video-ati being quite up to snuff, so Catalyst drivers are in the AUR.