5 ms·
But the FSF GPL faq says they would have to release the keys: "The only time you would be required to release signing keys is if you conveyed GPLed software in
by 0x0 10y ago
But the FSF GPL faq says they would have to release the keys:
"The only time you would be required to release signing keys is if you conveyed GPLed software inside a User Product, and its hardware checked the software for a valid cryptographic signature before it would function. In that specific case, you would be required to provide anyone who owned the device, on demand, with the key to sign and install modified software on the device so that it will run."
https://www.gnu.org/licenses/gpl-faq.en.html#GiveUpKeys https://www.gnu.org/licenses/gpl-faq.en.html#GiveUpKeys
Sounds exactly like how iOS code signing works...?
- detaro 10y agoIt also says: If each instance of the device uses a different key, then you need only give each purchaser a key for that instance. Allowing each device to generate a second, local signing key and allowing the user to export it for signing modified components likely would fulfill this requirement. Most Apple devices probably already have some crypto module that could generate and manage such a key.
- 0x0 10y agoIt's pretty clear that a second, local signing key is absolutely not something Apple wants in its iOS ecosystem, because that would open up sideloading of apps bypassing the app store.
- detaro 10y agoTrue, they'd need a way to limit it to the GPL components for iOS devices, which makes it a lot more complex and ugly to implement. (I had mostly been thinking about macbooks, where the feature might be an easier sell)
- Someone 10y agoI don't see how one would limit it in any way. If they ship a binary and give you its signing key, you can change it into any binary you want and resign it, and the OS will have to accept it (if it doesn't, they aren't complying with the GPL because, apparently, they didn't give you the full effective signing key)
- detaro 10y agoYes, but they would want to have that key to be limited to only allow replacing of GPLv3 binaries. Just because I can demand a key to replace GPLv3 components doesn't mean I can demand a key to replace other software components, so the verification system has to be able to use different keys for different parts of the system. (If that is wrong, and I can demand a key for everything, then that is the obvious answer why we'll never see GPLv3 on there. Or even if it is unclear what the actual situation is)
- Someone 10y agoBut that means the OS will run any binary of which the creator, by signing it with that key, claims it is GPL3. That renders the entire system useless.
- davexunit 10y agoSo let's not blame the GPL! This is Apple's problem, not the GPL's, because they want to have full control over iPhone users.
- detaro 10y agoNobody in this specific comment chain has been blaming the GPL?