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
(b) doesn't work | 474 comments | Create New Account
Comments belong to whoever posts them. Please notify us of inappropriate comments.
(b) doesn't work
Authored by: tknarr on Friday, July 06 2012 @ 08:27 PM EDT

a) doesn't require the vendor to do any work. The OEM can do exactly that, pre-enroll the keys and use Canonical's images and not do any more work at all. The only thing they have to do to comply with the GPLv3 is select hardware that permits the user, not the OEM, to enroll their own keys or disable Secure Boot (and of course include the tools Canonical provides for generating keys and signing the bootloader). As I said, the GPLv3 requires that the OEM provide all the tools to let the user modify the software, it doesn't obligate the OEM to handhold the user through the process. It's up to the user to sign their own modified bootloader and enroll the keys.

The only problem, as I noted, is if the OEM elects to use a BIOS that doesn't permit users to modify the keys or disable Secure Boot. That is the only time a signing key would have to be disclosed to users. And there's no legitimate reason to select hardware that prevents the user from exercising control over their own property.

[ 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 )