View Single Post
Old 05-21-2019, 01:54 PM   #30
eddie.t.h
Addict
eddie.t.h is an accomplished Snipe hunter.eddie.t.h is an accomplished Snipe hunter.eddie.t.h is an accomplished Snipe hunter.eddie.t.h is an accomplished Snipe hunter.eddie.t.h is an accomplished Snipe hunter.eddie.t.h is an accomplished Snipe hunter.eddie.t.h is an accomplished Snipe hunter.eddie.t.h is an accomplished Snipe hunter.eddie.t.h is an accomplished Snipe hunter.eddie.t.h is an accomplished Snipe hunter.eddie.t.h is an accomplished Snipe hunter.
 
eddie.t.h's Avatar
 
Posts: 201
Karma: 123456
Join Date: Jan 2018
Device: Too Much Kindle :-)
Quote:
Originally Posted by DeKuns View Post
Thanks for the info!
So it is currently affecting Gen 1-2 only. I read here Gen 3 might inherit the same process in communicating to Amazon server:
https://www.turnkeylinux.org/blog/kindle-root



If you can analyze the debug file, then could you inform here what file that Amazon send from their CERT_SERVER_URL? This is where I saw my Kindle DX stop in registration process because it received a respond from the server that the file is not found. Thanks.
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.
eddie.t.h is offline   Reply With Quote