Hi
I'm doing enhancement to Android recovery feature for Freescale's i.MX
platform.
Main target is to add EXT3 partition support based on the original MTD
partition, and let android rootfs running on movi-nand or SD card can
do recovery.
As the normal recovery procedure, recovery service unpacks the
update.zip after reading update command. It reads the public key in /
res/keys from rootfs into a structure before apply the update-script:
typedef struct RSAPublicKey {
int len; /* Length of n[] in number of uint32_t
*/
uint32_t n0inv; /* -1 / n[0] mod 2^32 */
uint32_t n[RSANUMWORDS]; /* modulus as little endian array */
uint32_t rr[RSANUMWORDS]; /* R^2 as little endian array */
} RSAPublicKey;
This public key is used to decrypt the .SF file's signature stored
in .RSA file, and compare to the .SF file's SHA-1 digest. This makes
sure .SF file is correct.
So in our recovery implement, we will have own keystore, and create
own /res/keys.
But I can not find the res/keys file in the android source or, in the
recovery image which used to hack G1 to get root permission.
My question is:
1. Does the hacked recovery rootfs image remove this verification
codes? (As I dump the recovery binary, seems no "res/keys" symbol)
2. What's key file's format, and how to generate it from a
certification file?
Thanks.
BR
Xinyu Chen
--~--~---------~--~----~------------~-------~--~----~
unsubscribe: [email protected]
website: http://groups.google.com/group/android-porting
-~----------~----~----~----~------~----~------~--~---
