04f771dee4
Relax the requirement to have both seinfo and name specified for privapps. The original reason for requiring both was because, normally, a package can only be uniquely specified by both name and signature, otherwise package squatting could occur. However, privapps are pre-installed, so the concerns about the potential for package squatting are eliminated. This change will drastically simplify sepolicy configuration for priv-apps. Bug: 142672293 Test: Flashed a device with this build and verified com.google.android.permissioncontroller still runs in the permissioncontroller_app domain. Change-Id: I5bb2bf84b9db616c4492bd1402550821c70fdd07
29 lines
933 B
Plaintext
29 lines
933 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
|
|
|
|
[@NETWORK_STACK]
|
|
ALL : $MAINLINE_SEPOLICY_DEV_CERTIFICATES/networkstack.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
|
|
|