View Single Post
Old 08-11-2017, 04:12 PM   #2437
nicolasmart
Sometimes active.
nicolasmart ought to be getting tired of karma fortunes by now.nicolasmart ought to be getting tired of karma fortunes by now.nicolasmart ought to be getting tired of karma fortunes by now.nicolasmart ought to be getting tired of karma fortunes by now.nicolasmart ought to be getting tired of karma fortunes by now.nicolasmart ought to be getting tired of karma fortunes by now.nicolasmart ought to be getting tired of karma fortunes by now.nicolasmart ought to be getting tired of karma fortunes by now.nicolasmart ought to be getting tired of karma fortunes by now.nicolasmart ought to be getting tired of karma fortunes by now.nicolasmart ought to be getting tired of karma fortunes by now.
 
nicolasmart's Avatar
 
Posts: 132
Karma: 484026
Join Date: Mar 2015
Device: KT2, PW2
Quote:
Originally Posted by coplate View Post
You cannot sign the packages with the pubprodkey01.pem - that is the public production key part of a public-private keypair. Amazon holds the private key and does not give it out... that is the whole point.

The signatures are generated with amazons private key when they make then. then the updates are checked by using the public key with some mathematics I do not understand.

KindleTool probably has an error using the public key as a private key, and fails, defaulting to the developer private key that the folks on this forum have put together.


If we could sign things with amazons production key, we wouldn't need to jailbreak
Yup, that's what I just thought. So, is it a dead end?!

Surely there should be a way of making an update package, containing:

-uboot from 5.8.10
-uImage from 5.8.10
-rootfs from 5.6.0 (factory).

I don't know...
nicolasmart is offline   Reply With Quote