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
Canonical'sDuty to Distributors | 474 comments | Create New Account
Comments belong to whoever posts them. Please notify us of inappropriate comments.
Canonical'sDuty to Distributors
Authored by: Anonymous on Tuesday, July 03 2012 @ 03:05 AM EDT
I was thinking of the case where the distributor provides hardware
preloaded with Ubuntu, or advertised as Linux capable. After all
Canonical are in the business of selling Linux system support,
which I assume means they have some notion of what/whose
hardware is suitable. And that implies they have an understanding
with the hardware suppliers that goes beyond the exchange of
banknotes in brown paper bags.

[ Reply to This | Parent | # ]

  • I don't disagree - Authored by: Anonymous on Wednesday, July 04 2012 @ 01:27 AM EDT
    • But maybe not - Authored by: pem on Wednesday, July 04 2012 @ 10:33 AM EDT
      • But maybe not - Authored by: Wol on Thursday, July 05 2012 @ 05:09 PM EDT
        • Sure - Authored by: pem on Friday, July 06 2012 @ 10:44 AM EDT
Canonical'sDuty to Distributors
Authored by: Anonymous on Thursday, July 05 2012 @ 09:08 AM EDT
IOW, the problem would have been avoided by the distributor allowing the owner to turn off secure boot or add his own keys.

You're assuming that the distributor is actually making the motherboard and firmware.

More likely, they are an OEM assembling generic parts.

Let's face it, secure boot isn't a problem if it is easily turned off - the worry is that because of the market dominance of Windows there is no particular incentive for motherboard makers to make it easy, or even possible to do this on their mass-market motherboards. The choice for OEMs could be - live with secure boot or use a more expensive 'specialist' motherboard that makes your product uncompetetive.

Also the typical end-user (a) isn't competent to change motherboard firmware settings, or manage keys, and (b) isn't going to like the idea of disabling a security setting. So this 'feature' will only be there to satisfy geeks and GPL lawyers - and no OEM is going to want to increase costs for that.

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