Ugh, really hope Microsoft goes back to their 8/8.1 ways.
http://arstechnica.com/information-...ke-the-secure-boot-alt-os-lock-out-a-reality/
It's not difficult to imagine Microsoft doing incentives for OEMs willing to lock secure boot, or the OEMs themselves selling locked/unlocked ones but at different price points (that second bit is what I expect to happen, retailers charging a lot more for the option to turn Secure Boot off). Granted many people around here won't have problems as they custom build desktop PCs, but you can't exactly do the same for laptops (which is where this would affect me).
Of course, it doesn't completely rule out installing Linux on those "locked" machines.
The way I understand it, Microsoft could no longer supply signed bootloaders and stop anyone from installing Linux on the machines with Secure Boot enabled. With 8/8.1, Linux Foundation had to release a "convoluted" workaround before Microsoft finally signed their bootloader.
Those of you with long memories will recall a barrage of complaints in the run up to Windows 8's launch that concerned the ability to install other operating systems—whether they be older versions of Windows, or alternatives such as Linux or FreeBSD—on hardware that sported a "Designed for Windows 8" logo.
To get that logo, hardware manufacturers had to fulfil a range of requirements for the systems they built, and one of those requirements had people worried. Windows 8 required machines to support a feature called UEFI Secure Boot. Secure Boot protects against malware that interferes with the boot process in order to inject itself into the operating system at a low level. When Secure Boot is enabled, the core components used to boot the machine must have correct cryptographic signatures, and the UEFI firmware verifies this before it lets the machine start. If any files have been tampered with, breaking their signature, the system won't boot.
This is a desirable security feature, but it has an issue for alternative operating systems: if, for example, you prefer to compile your own operating system, your boot files won't include a signature that Secure Boot will recognize and authorize, and so you won't be able to boot your PC.
However, Microsoft's rules for the Designed for Windows 8 logo included a solution to the problem they would cause: Microsoft also mandated that every system must have a user-accessible switch to turn Secure Boot off, thereby ensuring that computers would be compatible with other operating systems. Microsoft's rules also required that users be able to add their own signatures and cryptographic certificates to the firmware, so that they could still have the protection that Secure Boot provides, while still having the freedom to compile their own software.
This all seemed to work, and the concerns that Linux and other operating systems would be locked out proved unfounded.
This time, however, they're not.
To get that logo, hardware manufacturers had to fulfil a range of requirements for the systems they built, and one of those requirements had people worried. Windows 8 required machines to support a feature called UEFI Secure Boot. Secure Boot protects against malware that interferes with the boot process in order to inject itself into the operating system at a low level. When Secure Boot is enabled, the core components used to boot the machine must have correct cryptographic signatures, and the UEFI firmware verifies this before it lets the machine start. If any files have been tampered with, breaking their signature, the system won't boot.
This is a desirable security feature, but it has an issue for alternative operating systems: if, for example, you prefer to compile your own operating system, your boot files won't include a signature that Secure Boot will recognize and authorize, and so you won't be able to boot your PC.
However, Microsoft's rules for the Designed for Windows 8 logo included a solution to the problem they would cause: Microsoft also mandated that every system must have a user-accessible switch to turn Secure Boot off, thereby ensuring that computers would be compatible with other operating systems. Microsoft's rules also required that users be able to add their own signatures and cryptographic certificates to the firmware, so that they could still have the protection that Secure Boot provides, while still having the freedom to compile their own software.
This all seemed to work, and the concerns that Linux and other operating systems would be locked out proved unfounded.
This time, however, they're not.
It's not difficult to imagine Microsoft doing incentives for OEMs willing to lock secure boot, or the OEMs themselves selling locked/unlocked ones but at different price points (that second bit is what I expect to happen, retailers charging a lot more for the option to turn Secure Boot off). Granted many people around here won't have problems as they custom build desktop PCs, but you can't exactly do the same for laptops (which is where this would affect me).
Of course, it doesn't completely rule out installing Linux on those "locked" machines.
Should this stand, we can envisage OEMs building machines that will offer no easy way to boot self-built operating systems, or indeed, any operating system that doesn't have appropriate digital signatures. This doesn't cut out Linux entirely—there have been some collaborations to provide Linux boot software with the "right" set of signatures, and these should continue to work—but it will make it a lot less easy.
Last edited: