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