decoration decoration
Stories

GROKLAW
When you want to know more...
decoration
For layout only
Home
Archives
Site Map
Search
About Groklaw
Awards
Legal Research
Timelines
ApplevSamsung
ApplevSamsung p.2
ArchiveExplorer
Autozone
Bilski
Cases
Cast: Lawyers
Comes v. MS
Contracts/Documents
Courts
DRM
Gordon v MS
GPL
Grokdoc
HTML How To
IPI v RH
IV v. Google
Legal Docs
Lodsys
MS Litigations
MSvB&N
News Picks
Novell v. MS
Novell-MS Deal
ODF/OOXML
OOXML Appeals
OraclevGoogle
Patents
ProjectMonterey
Psystar
Quote Database
Red Hat v SCO
Salus Book
SCEA v Hotz
SCO Appeals
SCO Bankruptcy
SCO Financials
SCO Overview
SCO v IBM
SCO v Novell
SCO:Soup2Nuts
SCOsource
Sean Daly
Software Patents
Switch to Linux
Transcripts
Unix Books

Gear

Groklaw Gear

Click here to send an email to the editor of this weblog.


You won't find me on Facebook


Donate

Donate Paypal


No Legal Advice

The information on Groklaw is not intended to constitute legal advice. While Mark is a lawyer and he has asked other lawyers and law students to contribute articles, all of these articles are offered to help educate, not to provide specific legal advice. They are not your lawyers.

Here's Groklaw's comments policy.


What's New

STORIES
No new stories

COMMENTS last 48 hrs
No new comments


Sponsors

Hosting:
hosted by ibiblio

On servers donated to ibiblio by AMD.

Webmaster
"This is all a huge waste of time." | 246 comments | Create New Account
Comments belong to whoever posts them. Please notify us of inappropriate comments.
Linus Torvalds Suggests How To Handle UEFI Secure Boot Crisis
Authored by: jbb on Friday, March 01 2013 @ 11:28 PM EST
That's fine if you are creating everything yourself (like Linus) but don't you see a need for being able to trust someone besides yourself or Microsoft? ISTM that is what MG is talking about.

The idea is that you can put your distro's public key into your firmware and then the system will only trust code signed by the distro's private key. You can add your own key so the system will trust anything by your distro and anything you sign yourself. Even if you don't want to use such a solution yourself, can't you see that there might be a large and legitimate demand for something like this?

In order for this to happen, the kernel needs to copy (and use) keys from the firmware. This is what Linus is objecting to. As long as the user/owner has control of those keys I don't see what the problem is.

---
Our job is to remind ourselves that there are more contexts
than the one we’re in now — the one that we think is reality.
-- Alan Kay

[ Reply to This | Parent | # ]

"This is all a huge waste of time."
Authored by: Anonymous on Saturday, March 02 2013 @ 07:20 AM EST
Agreed, "This is all a huge waste of time.".

[ Reply to This | Parent | # ]

Linus Torvalds Suggests How To Handle UEFI Secure Boot Crisis
Authored by: Anonymous on Saturday, March 02 2013 @ 01:58 PM EST
b) To deliver a computer that ... Microsoft trusts, such that you can't steal their precious DRM protected products.

From what I understand, the primary way of pirating MS Windows 7 currently is to run a shim loader that in turn loads Windows 7 and satisfies all its copy protection checks. A computer that only uses UEFI secure boot would prevent that as the shim loader would either not be signed in the first place, or could be black listed later (as part of a Windows update). That would lock down PCs to the same degree as consoles.

At the moment, UEFI is optional on x86 PCs. That however is because MS Windows XP is still under official support and still widely used in business, so there has to be some transition period where PCs will support both traditional BIOS and UEFI secure boot.

After Windows XP is out of support and business use has dropped to negligible levels (one will follow the other quite closely), then there will be no need for traditional BIOS. MS Windows Vista has already been airbrushed out of the official Microsoft history like Stalin's colleagues were from party photographs, so it doesn't matter. Once Windows XP is gone, Microsoft can change the requirements for Windows 9 or Windows 10 to require that only UEFI secure boot is possible. At that point, PCs will be locked down like game consoles.

Indeed there may be no need for Microsoft to officially require PCs makers to stop supporting "unlocked" PCs. Once Microsoft no longer make it an official requirement that Pcs can be unlocked, the PC makers will delete that firmware themselves as a cost saving. Either that, or those functions simply won't work because nobody at the PC makers will care enough about them to make them work. There are already PCs on the market which will not boot most Linux distros even if the PC is unlocked because the boot firmware menu checks to only allow either Microsoft Windows or Red Hat Linux.

In the long run, the only guaranty that desktop and laptop computers will be able to boot Linux is if there are enough people using it to make it a worthwhile market for at least some vendors and if there is an alternative firmware available that is easy to install. If that doesn't happen, then the only way you will be able to use Linux in future is on a server, tablet, or phone.

[ Reply to This | Parent | # ]

Groklaw © Copyright 2003-2013 Pamela Jones.
All trademarks and copyrights on this page are owned by their respective owners.
Comments are owned by the individual posters.

PJ's articles are licensed under a Creative Commons License. ( Details )