4 ms·
Microsoft's Secure Boot in the UEFI isn't SELinux[0]. It's actually not difficult to get VBox/VMWare to play nice with secure boot[1], once you've generated you
by Eiriksmal 10y ago
Microsoft's Secure Boot in the UEFI isn't SELinux[0]. It's actually not difficult to get VBox/VMWare to play nice with secure boot[1], once you've generated your custom signing keys. I keep a .sh on my machine to sign the latest kernel after each `dnf update`. Weirdly, my laptop had trouble booting with Secure Boot disabled so I was forced to figure out how to get them to play nice.
[0] https://docs.fedoraproject.org/en-US/Fedora/18/html/UEFI_Secure_Boot_Guide/chap-UEFI_Secure_Boot_Guide-What_is_Secure_Boot.html https://docs.fedoraproject.org/en-US/Fedora/18/html/UEFI_Sec...
[1] http://gorka.eguileor.com/vbox-vmware-in-secureboot-linux/ http://gorka.eguileor.com/vbox-vmware-in-secureboot-linux/
- josteink 10y ago> Microsoft's Secure Boot in the UEFI isn't SELinux You may be absolutely right here and I may have incorrectly conflated the issues. That said it's UEFI secure boot, not Microsoft secure boot. Microsoft helped create the spec, but anyone is free to implement it and use it without any Microsoft involvement. Maybe you're conflating some things too ;)