"Delays beset the Linux Foundation's Secure Boot workaround"
Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Linux aficionados who have been watching the Windows 8 Secure Boot saga unfold in recent months will likely remember that the Linux Foundation itself last month unveiled plans for a workaround that would help Linux users get past the problem.
“We have the code for the Linux Foundation pre-bootloader in place,” Bottomley wrote in a blog post. “However, there was a delay while we got access to the Microsoft signing system.
“I’m still not sure what the actual problem is, but ... I suspect that the binary is signed with a generic Microsoft key instead of a specific (and revocable) key tied to the Linux Foundation,” Bottomley explained.
In any case, the end result is that, despite paying its $99 fee, the Linux Foundation so far still does not have a validly signed pre-bootloader.
A public solution
Causing all this turmoil, of course, is the fact that Windows 8 hardware will come with Secure Boot enabled in the Unified Extensible Firmware Interface (UEFI), meaning that only operating systems with an appropriate digital signature will be able to boot. Ubuntu, Fedora, and SUSE Linux are all among the Linux distributions that have unveiled plans for working around the problem, which has also drawn attention from the Free Software Foundation.
Back in July Bottomley announced an effort among Linux developers to brainstorm fresh solutions, leading to the October announcement that the Linux Foundation would obtain a Microsoft Key and sign a small pre-bootloader that would enable Linux to boot on such hardware.
Location: Northeastern Michigan, where Carhartt is a Designer Label
Distribution: Slackware 32- & 64-bit Stable
Posts: 3,541
Rep:
I'm starting to think that we're going to have to abandon the inexpensive; i.e., mass market Windows compatible, platforms for more robust; i.e., non-UEFI, ones.
Hey! Maybe Motorola has modernized 68000 and 88000 chip families in the vaults! Wouldn't that be sumpin'; bye-bye Intel, best of luck to ya.
Nah.
Maybe IBM, H-P, somebody will step up and tell Microcrap to pound sand... nah, ain't gonna happen.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.