View Single Post
Old 05-21-2019, 03:53 PM   #32
DeKuns
Connoisseur
DeKuns puts his or her pants on both legs at a time.DeKuns puts his or her pants on both legs at a time.DeKuns puts his or her pants on both legs at a time.DeKuns puts his or her pants on both legs at a time.DeKuns puts his or her pants on both legs at a time.DeKuns puts his or her pants on both legs at a time.DeKuns puts his or her pants on both legs at a time.DeKuns puts his or her pants on both legs at a time.DeKuns puts his or her pants on both legs at a time.DeKuns puts his or her pants on both legs at a time.DeKuns puts his or her pants on both legs at a time.
 
Posts: 89
Karma: 133654
Join Date: Apr 2019
Device: Kindle DX Graphite
Quote:
Originally Posted by eddie.t.h View Post
Unfortunately, the debug file does not contain anything about registration. Maybe too much time has passed. In the location /var/local/java/prefs/certs I have two files: client.p12 client.pem
client.pem looks like a normal ssh key but from what I see it contains the device serial number, motherboard number, etc.
client.p12 is totally unreadable.
Thanks, Eddie! I also dive-in into my Kindle DX. I can confirmed that /var/local/java/prefs/certs is now consist "client.p12". This seemed to be the `private' certificate of the Kindle. When it runs in my Windows PC, "client.p12" trigger a window that I never saw before. It looks like a wizard to create a certificate. So yes, Amazon firmware 2.5.8 has at least one bug. It delete the `private key' from the device if it is factory reset.

About the `private' and `general' certificate, @knc1 you are right! On creating an image backup, I have tested Yifanlu's tool works for Kindle DX. I will make an image backup. Just in case days like these happen again.

Last edited by DeKuns; 05-21-2019 at 03:55 PM.
DeKuns is offline   Reply With Quote