i.MX ProcessorsのトピックRe: Proper Way to replace test keys

Proper Way to replace test keys

michaelrobbelot — Wed, 03 Apr 2013 13:04:57 GMT

Everyone,

What is the proper way to replace the test keys build/target/product/security? When I replace the test keys with our organization's generated release keys, the build will keep asking for the shared, test, etc., keys whenever signapk is called. I tried using a combination of the instructions in the Advanced User Guide and How to replace the release keys in the AOSP .

Michael Robbeloth

Re: Proper Way to replace test keys

lily_zhang — Thu, 11 Apr 2013 07:25:31 GMT

Hello, Michael:

I made one experiment by following the suggestions of guideline and it can work. For example:

1. Created and switch to the folder vendor/fsl/security/sabresd_6dq/

2. Created keys and key in the passwords:

sh development/tools/make_key platform '/C=US/ST=California/L=Mountain View/O=Android/OU=Android/CN=Android/emailAddress=android@android.com'
sh development/tools/make_key media '/C=US/ST=California/L=Mountain View/O=Android/OU=Android/CN=Android/emailAddress=android@android.com'
sh development/tools/make_key shared '/C=US/ST=California/L=Mountain View/O=Android/OU=Android/CN=Android/emailAddress=android@android.com'
sh development/tools/make_key releasekey '/C=US/ST=California/L=Mountain View/O=Android/OU=Android/CN=Android/emailAddress=android@android.com'

3. In android root folder, run the command and key in passwords:

~/android/build/tools/releasetools/sign_target_files_apks -d vendor/fsl/security/sabresd_6dq/ out/dist/sabresd_6dq-target_files.zip signed-target_files.zip

4. The command can run well.

Re: Proper Way to replace test keys

michaelrobbelot — Thu, 11 Apr 2013 11:38:26 GMT

Xiaoli,

I have followed this procedure for updates and ran into problems (see my other message on signed ota updates). For full builds that we will program into our boards with the MfgTool, we need to be able to use our keys and not the test keys. However, when those keys are replaced, each build script will keep asking me to enter the password corresponding to the media, shared, etc., keys. The desired behavior is to replace the test keys with our organization's keys (generated using the above procedure) and not have the build keep asking for those passwords.

Michael Robbeloth

Re: Proper Way to replace test keys

lily_zhang — Thu, 11 Apr 2013 12:35:20 GMT

Are you using the same password when you generate keys?

Re: Proper Way to replace test keys

michaelrobbelot — Thu, 11 Apr 2013 13:00:36 GMT

I'm using different passwords for each key

Michael Robbeloth

Re: Proper Way to replace test keys

lily_zhang — Thu, 11 Apr 2013 13:48:32 GMT

Hope I caught your meaning.

You just need to generate keys once. These passwords will be used when you run sign_target_files_apks.

Best Regards

Lily Zhang

Freescale MPU Support

Re: Proper Way to replace test keys

YixingKong — Mon, 15 Apr 2013 09:30:41 GMT

Michael

If your questin had been answered please click Correct Answer.

Thanks,

Yixing