View Single Post
Old 02-11-2016, 12:27 PM   #10
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
for a long time there was confusion here because we had two things called: Jail break.

One (what we still call a jail break) put our (MR dev) signature certificate into the Kindle's certificate store.

The other, updated the Java application keystore, and also installed that *.jar file to "break" out of the Java jail.

Due to that confusion, it got re-named MKK (Mobileread Kindlet Kit - or some such).

Then, since it was almost **always** installed on jail broken Kindles, the "device jailbreak" got expanded to also bundle the Java Kindlet jailbreak and install it at the same time.

History.

= = = =

You will have to sign your Kindlet's jar files (details in that wiki page link above) -
That is where the 'Combined Keystore' thingy comes into play - during the signing.

Kindlets are just *.azw2 documents that drop into the /documents folder so you don't need to create an update_*.bin file for them with KindleTool.

Anything that needs to be model locked and/or will alter the filesystem tree outside of user storage needs to be packaged as an update_*.bin file.
KindleTool will do that for you.
It has the private signature key built into it.
knc1 is offline   Reply With Quote