View Single Post
Old 08-22-2019, 05:12 PM   #56
knc1
Going Viral
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
Quote:
Originally Posted by WaseemAlkurdi View Post
So the factory firmware places its own header and signature somewhere on the eMMC and the selfsame firmware reads the signature and header to verify itself?
Or is there something I don't understand?
All package files with the name format of: update_*.bin have a cryptographic signature attached.
The signature uses public key (key pairs, public and private) encryption.
The Kindles only have the public key, the update_*.bin files are created with the private key.

You can read all the gory details in "KindleTool".
That utility is able to package and un-package the update_*.bin files, both Amazon and Mobileread.

Of course, Amazon does not provide us with their private key so we have to use our own key-pair.

Last edited by knc1; 08-22-2019 at 05:17 PM.
knc1 is offline   Reply With Quote