cc39f63773
Divide policy into public and private components. This is the first step in splitting the policy creation for platform and non-platform policies. The policy in the public directory will be exported for use in non-platform policy creation. Backwards compatibility with it will be achieved by converting the exported policy into attribute-based policy when included as part of the non-platform policy and a mapping file will be maintained to be included with the platform policy that maps exported attributes of previous versions to the current platform version. Eventually we would like to create a clear interface between the platform and non-platform device components so that the exported policy, and the need for attributes is minimal. For now, almost all types and avrules are left in public. Test: Tested by building policy and running on device. Change-Id: Idef796c9ec169259787c3f9d8f423edf4ce27f8c
26 lines
851 B
Plaintext
26 lines
851 B
Plaintext
#
|
|
# 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 : $DEFAULT_SYSTEM_DEV_CERTIFICATE/platform.x509.pem
|
|
|
|
[@MEDIA]
|
|
ALL : $DEFAULT_SYSTEM_DEV_CERTIFICATE/media.x509.pem
|
|
|
|
[@SHARED]
|
|
ALL : $DEFAULT_SYSTEM_DEV_CERTIFICATE/shared.x509.pem
|
|
|
|
# Example of ALL TARGET_BUILD_VARIANTS
|
|
[@RELEASE]
|
|
ENG : $DEFAULT_SYSTEM_DEV_CERTIFICATE/testkey.x509.pem
|
|
USER : $DEFAULT_SYSTEM_DEV_CERTIFICATE/testkey.x509.pem
|
|
USERDEBUG : $DEFAULT_SYSTEM_DEV_CERTIFICATE/testkey.x509.pem
|
|
|