|
** IF ** a court where to decide that the intent of the dizzy language was to allow after-market modification of the GPLv3 software that is part of the product's firmware . . . .
Then one way to meet that intent would be -
We (Mobile Read Dev.s) send Amazon our public key of the Dev. Key-Pair, along with its 'install scripting' -
Amazon wraps (packages) our submission using their Private Key-Pair, returns it to us for distribution.
I.E: An Amazon signed, device jailbreak certificate.
One which the normal system updater could install for the end-user.
With that procedure, nobody reveals any 'secret' part of their key-pairs.
I don't think it would meet the language of the license, but would it meet the 'intent'?
I don't know.
- - - -
Also included in the license text is some strong language about who 'owns' the device - -
Which could lead into consideration of the battle we have been fighting with Amazon:
I.E: The purchaser owns the device, but who owns its behavior and functions ?
Amazon clearly behaves as if they think they own the behavior and function of the device ;
We (the devs) clearly believe that the owner of the device does.
|