News for hackers. Stuff that matters.
Re:D-Link publishes code-signing private keys by mistake by tzs on Thursday September 17, 2015 @05:06PM (#10236068)
Yet in GPLv3, where they could have explicitly made it so that the modified code must be able to be installed back on the original hardware, they declined to do so in the general case. The anti-tivoization clause instead was written narrowly to only apply when the object code was conveyed "as part of a transaction in which the right of possession and use of the User Product is transferred to the recipient in perpetuity or for a fixed term (regardless of how the transaction is characterized)".

Note that this means that I could sell a device that only runs signed code and could separately sell signed apps for that device that the user can buy and install later, and as long as the code that ships with the device is not GPLv3, I could use GPLv3 code in the signed apps and would NOT be required to release signing keys under GPLv3.

(The Apple App store incompatibility with GPLv3 has nothing to do with the app signing requirements. It is due to the terms of service that users are required to agree to in order to access the store. These impose what the GPL considers to be additional, incompatible conditions).

It seems odd, if they felt the way you think they do, that they would have written this so narrowly.

There are no comments on this comment yet.