Linked by Thom Holwerda on Fri 23rd Sep 2011 22:22 UTC, submitted by kragil
Windows The story about how secure boot for Windows 8, part of UEFI, will hinder the use of non-signed binaries and operating systems, like Linux, has registered at Redmond as well. The company posted about it on the Building Windows 8 blog - but didn't take any of the worries away. In fact, Red Hat's Matthew Garrett, who originally broke this story, has some more information - worst of which is that Red Hat has received confirmation from hardware vendors that some of them will not allow you to disable secure boot.
Thread beginning with comment 490586
To read all comments associated with this story, please click here.
Propose solutions, don't bitch ...
by MacTO on Sat 24th Sep 2011 06:54 UTC
Member since:

UEFI has Microsoft's blessings, so it is going to happen.

There are also many reasons to implement secure boot, ranging from the legitimate (security is a very real concern on modern computers) to the illegitimate (anything proposed by the marketing department).

I'm also fairly certain that bitching about it ain't going to make it go away. But maybe we can propose coherent solutions that will allow our voice to be heard.

While I don't know the answers, here are two suggestions on my end:

Create a registry of devices where secure boot can be disabled and where there aren't restrictions on modifying the hardware. It won't force companies to introduce open hardware, but a few companies will produce open hardware to serve particular segments of the market. (This isn't exactly as complex as supporting Linux after all, since they're only providing an option to disable a feature.)

Maybe an independent bootloader could be implemented, one where the maintainers have a set of keys that hardware vendors are willing to distribute with their devices. They may have to play by the vendors rules while developing the bootloader, but that shouldn't be a problem as long as the OS developers don't have to play by the vendors rules.

So what is your proposed, and preferably non-confrontational, solution.

Reply Score: 2

BluenoseJake Member since:

But bitching about it just might make it go away. In the 90s, Intel tried to implement a processor id, and the tech world went nuts, and they were forced to make it optional.

Just recently, Apple wrote a new version of Final Cut Pro, and it was (by all accounts, I don't use it, I don't do video) crippled compared to previous versions. It's users were very vocal, and now Apple is quietly selling the old version again, and are putting out updates to address some of the issues.

The squeaky wheel gets the grease, ya know.

Reply Parent Score: 3