A Developing UEFI Secureboot Situation
We've been working to provide an alternative to the Microsoft key, so that the entire free software ecosystem is not dependent on Microsoft's goodwill for access to modern PC hardware. We originally flagged the UEFI / SecureBoot transition as a major problem for free software, we lead the efforts to shape the specification in a more industry-friendly way, and we're pressing OEM partners for options that will be more broadly acceptable than Red Hat's approach. SecureBoot retains flaws in its design that will ultimately mandate that Microsoft's key is on every PC (because of core UEFI driver signing). That, and the inability of SecureBoot to support multiple signatures on critical elements means that options are limited but we continue to seek a better result. Mark
It would seem that Canonical is putting more thought into the UEFI Secureboot situation and not jumping to the conclusion of buying a Microsoft Key which appears to be the “Red Hat Way” if you will. It will be interesting to see how the Open Source Community as a whole addresses the Windows 8 UEFI Secureboot concerns and how OEM’s will respond both to Microsoft’s demands and the Open Source Communities requests.
Surely other communities such as Linux Mint, Arch and Debian must also be wondering how they will proceed?