View Single Post
Old 02-23-2011, 10:58 AM   #123
dsmid
Linux devotee
dsmid ought to be getting tired of karma fortunes by now.dsmid ought to be getting tired of karma fortunes by now.dsmid ought to be getting tired of karma fortunes by now.dsmid ought to be getting tired of karma fortunes by now.dsmid ought to be getting tired of karma fortunes by now.dsmid ought to be getting tired of karma fortunes by now.dsmid ought to be getting tired of karma fortunes by now.dsmid ought to be getting tired of karma fortunes by now.dsmid ought to be getting tired of karma fortunes by now.dsmid ought to be getting tired of karma fortunes by now.dsmid ought to be getting tired of karma fortunes by now.
 
dsmid's Avatar
 
Posts: 598
Karma: 2069047
Join Date: Feb 2011
Device: Kindle 3, Kindle 4B, Kindle PW2
Quote:
Originally Posted by jlove View Post
@dsmid

im sorry if im wrong, i did get it that way. So why does the new jailbreak uninstall the update_provider hack? I thought because the jailbreak does include that?
It's because both hacks shuffle the keys and nasty conflicts might appear.
Jailbreak has different naming scheme for stored keys, it names them pubprodkey0*.amazon.pem and pubprodkey0*.hack.pem. On boot it copies appropriate keys to pubprodkey0*.pem (the only possible name for valid key on 3.1).
But the .pem extensions makes all the keys valid on 3.0.x.

OTOH Updates Provider hack names the stored keys like this:
pubprodkey0*.pem.amazon and pubprodkey0*.pem.hack.
That excludes them from '*.pem' glob in 3.0.x's update script.
dsmid is offline   Reply With Quote