|
|
|
| Authored by: pem on Monday, July 02 2012 @ 08:46 PM EDT |
If Ubuntu provides object code specifically for use in a User Product as part of
the transaction which transferred the User product to the user (which
transaction could, I think, theoretically be easily stretched to cover code
provided as contracted upgrades for the warranty period), then Ubuntu has to
provide "installation information" which is defined in the GPL to
include any information (including keys if necessary) required to install
modified software on the system.
As Ubuntu themselves said, they are worried about the computer vendor screwing
up. How does that work? I dunno, but here's my speculation about the screwup
path:
1) Vendor ships device preloaded with Ubuntu and Canonical's public key.
2) User gets an upgrade from Canonical, which he is entitled to as per the
implied warranty and the vendor's contract with Canonical.
3) Oopsie! Turns out the vendor goofed and other keys can't be loaded, and
secure boot can't be disabled.
4) Canonical is now on the hook to let the user modify the GPLed code and
reinstall it on the user's system.[ Reply to This | Parent | # ]
|
|
|
|
|
