That procedure just helps you create your own signing keys, which you use with signapk.jar to sign apks or updates, not .img files directly.
On Tue, Jul 20, 2010 at 4:24 AM, [email protected] < [email protected]> wrote: > Hi All, > > In the file "build/target/product/security/README", it is mentioned as > following: > > ***** > signing using the openssl commandline (for boot/system images) > -------------------------------------------------------------- > > 1. convert pk8 format key to pem format > % openssl pkcs8 -inform DER -nocrypt -in testkey.pk8 -out > testkey.pem > > 2. create a signature using the pem format key > % openssl dgst -binary -sha1 -sign testkey.pem FILE > FILE.sig > ********* > > 1. Can this procedure be used to sign bootloader/kernel i.e Can I > provide boot.img/system.img as the input files for step 2? > > 2. If answer to previous question is yes, is there additional > procedure to take care for building bootloader/kernel? > > 3. Is there any detailed documentation on this? > > > PS: This is posted in android-security-discuss group as well; Posting > this query in android-kernel group for better visibility. > > -- > unsubscribe: > [email protected]<android-kernel%[email protected]> > website: http://groups.google.com/group/android-kernel -- unsubscribe: [email protected] website: http://groups.google.com/group/android-kernel
