4 ms·
When secure boot started to go mainstream there was a lot of FUD that it was really just a mechanism to lock out alternative OSes. The reality is that hardware
by PragmaticPulp 6y ago
When secure boot started to go mainstream there was a lot of FUD that it was really just a mechanism to lock out alternative OSes.
The reality is that hardware manufactures do not care what OS you run, as long as it doesn’t result in costly hardware returns or endless support calls. This is why hardware typically has options to disable OS-specific. secure boot, but it requires some technical steps that average users won’t accidentally stumble upon.
The M1 macs were never locked down, either. Apple has said that Microsoft can make Windows builds for them if they’d like. Linux on M1 macs is only a matter of time.
Secure boot is a net win for everyone. Having an option to disable it lets the 0.01% of people who want to run Linux use the hardware too.
- officeplant 6y agoFrom what I've been made to understand by friends at Apple all they have to do is figure out iBoot. They suspect we'll have linux on M1 macs within the next 6 months.
- ryukafalz 6y ago>When secure boot started to go mainstream there was a lot of FUD that it was really just a mechanism to lock out alternative OSes. It wasn't just FUD. Microsoft has changed their tune on this over the years, but it used to be that their certification requirements mandated that users could not disable secure boot on ARM devices: https://arstechnica.com/information-technology/2012/01/microsoft-mandating-secure-boot-on-arm-making-linux-installs-difficult/ https://arstechnica.com/information-technology/2012/01/micro... If that were still their policy today, it would make projects like this nearly impossible.
- vetinari 6y agoExcept it was not FUD: see WinRT machines, which used Secure Boot and didn't allow neither MOK enrollment nor disabling Secure Boot.