diff options
| author | 2018-12-24 11:31:58 +0900 | |
|---|---|---|
| committer | 2019-01-11 13:35:56 +0900 | |
| commit | 9335a26cbd7f003798220e3c24814a1655fc84b3 (patch) | |
| tree | aec010bb812487ee463da2809cac28ea6e733109 /java/java_test.go | |
| parent | 709a3294519cc9e07aa6a96144a231d6d60b1814 (diff) | |
APEXes can be signed with devkeys
When PRODUCT_DEFAULT_DEV_CERTIFICATE is set to /vendor/foo/devkeys/test,
then the public/private key pairs for an apex_key is searched at
/vendor/foo/devkeys directory.
To be specific,
/system/timezone/Android.bp:
apex_key {
name: "timezone.key",
public_key: "com.android.tzdata.avbpubkey",
private_key: "com.android.tzdata.pem",
}
When PRODUCT_DEFAULT_DEV_CERTIFICATE isn't set, the keys are searched at
/system/timezone, which is the path where Android.bp is located.
With PRODUCT_DEFAULT_DEV_CERTIFICATE set to /vendor/foo/devkeys/test,
the keys are searched at /vendor/foo/devkeys.
Bug: 121224311
Test: m (apex_test updated)
Test: m with crosshatch (PRODUCT_DEFAULT_DEV_CERTIFICATE is set to
/vendor/google/...)
Test: m with cheets (PRODUCT_DEFAULT_DEV_CERTIFICATE is set, but there
is no apex key there. The product is with TARGET_FLATTEN_APEX := true)
Change-Id: I213bbb96c433d851f9cc982871459fd7fb4fe47d
Diffstat (limited to 'java/java_test.go')
0 files changed, 0 insertions, 0 deletions