A Redhat employee has gone on record to speculate that OEM machines that ship with copies of Windows 8 may lock out support for Linux installations.
The claims focus on the new UEFI secure boot protocol that is part of a new wave of system firmware Microsoft plans to support in Windows 8. Matthew Garrett, a power management and mobile Linux developer at Red Hat, revealed his concerns in a blog post earlier this week. “Microsoft requires that machines conforming to the Windows 8 logo program and running a client version of Windows 8 ship with secure boot enabled,” says Garrett.
The Secure Boot technology means that OEMs must ship their systems with UEFI keys that will allow the installation and boot of Windows 8. Garrett explains that there’s two ways OEMs and Microsoft could approach this. Windows could be signed with a Microsoft key and the public part of that key would ship with all systems or each OEM would include their own key and sign the pre-installed version of Windows 8. “The second approach would make it impossible to run boxed copies of Windows on Windows logo hardware,” notes Garrett. It would also make it impossible to install future versions of Windows unless an OEM provided a new signed copy.
The approach would also mean that systems that ship with just OEM and Microsoft keys could not boot a standard copy of Linux. ZDNet’s Mary Jo Foley noticed that Microsoft revealed in a BUILD session on UEFI that the following requirements must be met for Windows 8:
- All firmware and software in the boot process must be signed by a trusted Certificate Authority (CA)
- Required for Windows 8 client
- Does not require a Trusted Platform Module (TPM)
- Reduces the likelihood of bootkits, rootkits and ransomware

Microsoft's Windows 8 Secure Boot requirements
Garrett does note that Red Hat and others could provide signed versions of Linux but that this approach poses several problems. He explains that Linux distributions would need a non-GPL bootloader which differs throughout GPLv3 and v2 requirements. “Secondly, in the near future the design of the kernel will mean that the kernel itself is part of the bootloader. This means that kernels will also have to be signed. Making it impossible for users or developers to build their own kernels is not practical,” he explains. The last hurdle is that Red Hat and others companies would have to get their keys included by every OEM.
The other option is for OEMs to allow end users to disable the feature. “There’s no indication that Microsoft will prevent vendors from providing firmware support for disabling this feature and running unsigned code,” notes Garrett. Despite this being an option for OEMs, it’s possible that some will offer the ability to disable the feature whilst others will not. Microsoft’s Samsung Windows 8 developer tablet includes the option to disable Secure Boot, a good indication of Samsung’s plans for the feature. Microsoft has refused to comment on the situation.