MobileRead Forums - View Single Post

knc1 · 08-28-2015, 04:53 PM

OK Amazon, record this transcript, you have to be dragged into the 21st. century.

Every registered Kindle has an owner account.
Every registered Kindle has a MailTo, e-mail address.
Every Kindle account has a credit card or other payment means associated with it.
You own/operate a for-profit store.
You own/operate the world's 134th largest supercomputer (that you admit to):
http://top500.org/list/2015/06/?page=2
I know, its a small one, only 26,500 cores - but still ....
You have the infrastructure in-place to receive e-mail documents from the owner of a registered Kindle, to process that document, and to return it by e-mail to that specific Kindle.
You have the infrastructure in-place to charge for that processing service.
You are prohibited by the terms and conditions of the GPLv3 license from using any GPLv3 licensed code.
Which is starting to make for some very sucky firmware now.

Now lets pretend that you are a for-profit, forward looking, high tech. company - -
You would like to fix that sucky code problem, and perhaps make a buck or two (per Kindle) in the process.

Here is the outline of what has to happen:

Using the Kindle's MailTo e-mail address, the owner sends you an "update package request" which contains their public key of a key pair certificate.
Your existing computer system wraps that public key in a standard (your standard) update package as the data payload.
Your system then returns that package to that owner's specific Kindle.
You debit the owner's account for a small processing fee.
The owner then can get this wrapped key either OTA or from their Kindle account storage.
The owner updates their Kindle with that package.

Now the Kindle owner can install any update package signed by the corresponding private key.

No mystery there - if they sent their request containing MR's public key, then they could install any of our stuff.
Or they could build and package their own stuff to be installed on their Kindle.
We make it easy - everything on our end is already done and available on-line (see: KindleTool).

Now, with this system in-place, you are very close to meeting the requirements of GPLv3 and you make a buck or two on every Kindle doing it.
Say hello,

Note that you have never revealed your private key to anything other than your super-computer(s).

Now, are you going to leave that money laying on the table or not?
We all thought you where a for-profit corporation.

08-28-2015, 04:53 PM	#1
knc1 Going Viral Posts: 17,212 Karma: 18210809 Join Date: Feb 2012 Location: Central Texas Device: No K1, PW2, KV, KOA	The no fuss, muss, or bother jail break OK Amazon, record this transcript, you have to be dragged into the 21st. century. Every registered Kindle has an owner account. Every registered Kindle has a MailTo, e-mail address. Every Kindle account has a credit card or other payment means associated with it. You own/operate a for-profit store. You own/operate the world's 134th largest supercomputer (that you admit to): http://top500.org/list/2015/06/?page=2 I know, its a small one, only 26,500 cores - but still .... You have the infrastructure in-place to receive e-mail documents from the owner of a registered Kindle, to process that document, and to return it by e-mail to that specific Kindle. You have the infrastructure in-place to charge for that processing service. You are prohibited by the terms and conditions of the GPLv3 license from using any GPLv3 licensed code. Which is starting to make for some very sucky firmware now. Now lets pretend that you are a for-profit, forward looking, high tech. company - - You would like to fix that sucky code problem, and perhaps make a buck or two (per Kindle) in the process. Here is the outline of what has to happen: Using the Kindle's MailTo e-mail address, the owner sends you an "update package request" which contains their public key of a key pair certificate. Your existing computer system wraps that public key in a standard (your standard) update package as the data payload. Your system then returns that package to that owner's specific Kindle. You debit the owner's account for a small processing fee. The owner then can get this wrapped key either OTA or from their Kindle account storage. The owner updates their Kindle with that package. Now the Kindle owner can install any update package signed by the corresponding private key. No mystery there - if they sent their request containing MR's public key, then they could install any of our stuff. Or they could build and package their own stuff to be installed on their Kindle. We make it easy - everything on our end is already done and available on-line (see: KindleTool). Now, with this system in-place, you are very close to meeting the requirements of GPLv3 and you make a buck or two on every Kindle doing it. Say hello, Note that you have never revealed your private key to anything other than your super-computer(s). Now, are you going to leave that money laying on the table or not? We all thought you where a for-profit corporation. Last edited by knc1; 08-28-2015 at 05:01 PM.