1 The following commands were used to generate the test key pairs: 2 3 development/tools/make_key testkey '/C=US/ST=California/L=Mountain View/O=Android/OU=Android/CN=Android/emailAddress=android (a] android.com' 4 development/tools/make_key platform '/C=US/ST=California/L=Mountain View/O=Android/OU=Android/CN=Android/emailAddress=android (a] android.com' 5 development/tools/make_key shared '/C=US/ST=California/L=Mountain View/O=Android/OU=Android/CN=Android/emailAddress=android (a] android.com' 6 development/tools/make_key media '/C=US/ST=California/L=Mountain View/O=Android/OU=Android/CN=Android/emailAddress=android (a] android.com' 7 8 The following standard test keys are currently included: 9 10 testkey -- a generic key for packages that do not otherwise specify a key. 11 platform -- a test key for packages that are part of the core platform. 12 shared -- a test key for things that are shared in the home/contacts process. 13 media -- a test key for packages that are part of the media/download system. 14 15 These test keys are used strictly in development, and should never be assumed 16 to convey any sort of validity. When $BUILD_SECURE=true, the code should not 17 honor these keys in any context. 18 19 20 signing using the openssl commandline (for boot/system images) 21 -------------------------------------------------------------- 22 23 1. convert pk8 format key to pem format 24 % openssl pkcs8 -inform DER -nocrypt -in testkey.pk8 -out testkey.pem 25 26 2. create a signature using the pem format key 27 % openssl dgst -binary -sha1 -sign testkey.pem FILE > FILE.sig 28 29 extracting public keys for embedding 30 ------------------------------------ 31 it's a Java tool 32 but it generates C code 33 take a look at commands/recovery/Android.mk 34 you'll see it running $(HOST_OUT_JAVA_LIBRARIES)/dumpkey.jar 35
