9af6f1bd59
This breaks the ability for users to have certs in many directories. Currently the design is to allow keys.conf to specify arbitrary locations for pem files, relative to the root of the Android tree. If users want to have a common prefix on all the keys, then they can export DEFAULT_SYSTEM_DEV_CERTIFICATE, and make that an environment variable in their keys.conf file. Signed-off-by: William Roberts <wroberts@tresys.com> Change-Id: I23455b891206cab6eca7db08ff3c28283f87c640 Signed-off-by: William Roberts <wroberts@tresys.com>
25 lines
839 B
Text
25 lines
839 B
Text
#
|
|
# Maps an arbitrary tag [TAGNAME] with the string contents found in
|
|
# TARGET_BUILD_VARIANT. Common convention is to start TAGNAME with an @ and
|
|
# name it after the base file name of the pem file.
|
|
#
|
|
# Each tag (section) then allows one to specify any string found in
|
|
# TARGET_BUILD_VARIANT. Typcially this is user, eng, and userdebug. Another
|
|
# option is to use ALL which will match ANY TARGET_BUILD_VARIANT string.
|
|
#
|
|
|
|
[@PLATFORM]
|
|
ALL : build/target/product/security/platform.x509.pem
|
|
|
|
[@MEDIA]
|
|
ALL : build/target/product/security/media.x509.pem
|
|
|
|
[@SHARED]
|
|
ALL : build/target/product/security/shared.x509.pem
|
|
|
|
# Example of ALL TARGET_BUILD_VARIANTS
|
|
[@RELEASE]
|
|
ENG : build/target/product/security/testkey.x509.pem
|
|
USER : build/target/product/security/testkey.x509.pem
|
|
USERDEBUG : build/target/product/security/testkey.x509.pem
|
|
|