drgreen/android_frameworks_base
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
android_frameworks_base/data/etc/privapp-permissions-platform.xml

353 lines
20 KiB
XML
Raw Normal View History

Control privileged permissions for priv-apps Added support for privapp-permissions config element. It allows to explicitly control what privileged permissions applications should be granted. Feature is controlled by ro.control_privapp_permissions property. Possible values: - 0/false, the feature is completely disabled - signature|privileged permissions are granted automatically without logging. *Default behavior* - 1/true, enforce that only whitelisted permissions are granted. Only devices with ro.control_privapp_permission=1 will pass CTS tests. Test: Manual Bug:31008485 Change-Id: I93a8c2782cc72b3953f32c237086d08d82ac0d5b
2016-11-09 14:32:27 -08:00
<?xml version="1.0" encoding="utf-8"?>
<!--
~ Copyright (C) 2016 The Android Open Source Project
~
~ Licensed under the Apache License, Version 2.0 (the "License");
~ you may not use this file except in compliance with the License.
~ You may obtain a copy of the License at
~
~ http://www.apache.org/licenses/LICENSE-2.0
~
~ Unless required by applicable law or agreed to in writing, software
~ distributed under the License is distributed on an "AS IS" BASIS,
~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
~ See the License for the specific language governing permissions and
~ limitations under the License
-->
<!--
This XML file declares which signature|privileged permissions should be granted to privileged
applications that come with the platform
-->
<permissions>
Update package name for ExtServices to whitelist permissions. Test: shared images in Camera to verify this. Change-Id: Iebbe7405afa7de5246e02d7dbdb84fb0f319db5f
2017-10-19 11:48:20 -07:00
<privapp-permissions package="android.ext.services">
<permission name="android.permission.PROVIDE_RESOLVER_RANKER_SERVICE" />
</privapp-permissions>
Updated the whitelist to match the state of platform apps Some apps in frameworks/base are only included in AOSP targets and discrepancies weren't discovered by CI tests. Test: manual Bug: 67718369 Change-Id: If88aa90f4dcab51b6e11562cadbe003948b6c149
2017-10-19 12:26:32 -07:00
<privapp-permissions package="com.android.apps.tag">
<permission name="android.permission.WRITE_SECURE_SETTINGS"/>
</privapp-permissions>
Control privileged permissions for priv-apps Added support for privapp-permissions config element. It allows to explicitly control what privileged permissions applications should be granted. Feature is controlled by ro.control_privapp_permissions property. Possible values: - 0/false, the feature is completely disabled - signature|privileged permissions are granted automatically without logging. *Default behavior* - 1/true, enforce that only whitelisted permissions are granted. Only devices with ro.control_privapp_permission=1 will pass CTS tests. Test: Manual Bug:31008485 Change-Id: I93a8c2782cc72b3953f32c237086d08d82ac0d5b
2016-11-09 14:32:27 -08:00
<privapp-permissions package="com.android.backupconfirm">
<permission name="android.permission.BACKUP"/>
<permission name="android.permission.CRYPT_KEEPER"/>
</privapp-permissions>
<privapp-permissions package="com.android.cellbroadcastreceiver">
<permission name="android.permission.INTERACT_ACROSS_USERS"/>
<permission name="android.permission.MANAGE_USERS"/>
<permission name="android.permission.MODIFY_PHONE_STATE"/>
<permission name="android.permission.READ_PRIVILEGED_PHONE_STATE"/>
<permission name="android.permission.RECEIVE_EMERGENCY_BROADCAST"/>
</privapp-permissions>
<privapp-permissions package="com.android.defcontainer">
<permission name="android.permission.ACCESS_CACHE_FILESYSTEM"/>
Clear identity to handle ALLOCATE_AGGRESSIVE. We're not actually clearing any files, only deciding how much free space is available, so we're fine assuming the remote caller has the permission. Test: builds, boots Bug: 37169076 Change-Id: I6cd42f77c43e9d2de40e2b8b937c7f2145f1b869
2017-04-14 16:28:59 -06:00
<permission name="android.permission.ALLOCATE_AGGRESSIVE"/>
Control privileged permissions for priv-apps Added support for privapp-permissions config element. It allows to explicitly control what privileged permissions applications should be granted. Feature is controlled by ro.control_privapp_permissions property. Possible values: - 0/false, the feature is completely disabled - signature|privileged permissions are granted automatically without logging. *Default behavior* - 1/true, enforce that only whitelisted permissions are granted. Only devices with ro.control_privapp_permission=1 will pass CTS tests. Test: Manual Bug:31008485 Change-Id: I93a8c2782cc72b3953f32c237086d08d82ac0d5b
2016-11-09 14:32:27 -08:00
<permission name="android.permission.INTERACT_ACROSS_USERS"/>
<permission name="android.permission.WRITE_MEDIA_STORAGE"/>
</privapp-permissions>
<privapp-permissions package="com.android.dialer">
<permission name="android.permission.ALLOW_ANY_CODEC_FOR_PLAYBACK"/>
<permission name="android.permission.CONTROL_INCALL_EXPERIENCE"/>
<permission name="android.permission.GET_ACCOUNTS_PRIVILEGED"/>
<permission name="android.permission.MODIFY_PHONE_STATE"/>
Updated the whitelist to match the state of platform apps Some apps in frameworks/base are only included in AOSP targets and discrepancies weren't discovered by CI tests. Test: manual Bug: 67718369 Change-Id: If88aa90f4dcab51b6e11562cadbe003948b6c149
2017-10-19 12:26:32 -07:00
<permission name="android.permission.STATUS_BAR"/>
Control privileged permissions for priv-apps Added support for privapp-permissions config element. It allows to explicitly control what privileged permissions applications should be granted. Feature is controlled by ro.control_privapp_permissions property. Possible values: - 0/false, the feature is completely disabled - signature|privileged permissions are granted automatically without logging. *Default behavior* - 1/true, enforce that only whitelisted permissions are granted. Only devices with ro.control_privapp_permission=1 will pass CTS tests. Test: Manual Bug:31008485 Change-Id: I93a8c2782cc72b3953f32c237086d08d82ac0d5b
2016-11-09 14:32:27 -08:00
<permission name="android.permission.STOP_APP_SWITCHES"/>
<permission name="com.android.voicemail.permission.READ_VOICEMAIL"/>
<permission name="com.android.voicemail.permission.WRITE_VOICEMAIL"/>
</privapp-permissions>
<privapp-permissions package="com.android.emergency">
Add permission whitelist for EmergencyInfo app. This is the "Emergency Info" screen available from the lock screen. It requires the CALL_PRIVILEGED permission in order for it to be able to place emergency calls. This can occur if a user adds an emergency number to their emergency contacts. Test: make checkbuild Bug: 76086838 Change-Id: I76e8318c5c05bbbbdf02d2c6951f742c3bd67ea6
2018-04-11 11:05:32 -07:00
<!-- Required to place emergency calls from emergency info screen. -->
<permission name="android.permission.CALL_PRIVILEGED"/>
Control privileged permissions for priv-apps Added support for privapp-permissions config element. It allows to explicitly control what privileged permissions applications should be granted. Feature is controlled by ro.control_privapp_permissions property. Possible values: - 0/false, the feature is completely disabled - signature|privileged permissions are granted automatically without logging. *Default behavior* - 1/true, enforce that only whitelisted permissions are granted. Only devices with ro.control_privapp_permission=1 will pass CTS tests. Test: Manual Bug:31008485 Change-Id: I93a8c2782cc72b3953f32c237086d08d82ac0d5b
2016-11-09 14:32:27 -08:00
<permission name="android.permission.MANAGE_USERS"/>
</privapp-permissions>
<privapp-permissions package="com.android.externalstorage">
<permission name="android.permission.MOUNT_UNMOUNT_FILESYSTEMS"/>
<permission name="android.permission.WRITE_MEDIA_STORAGE"/>
</privapp-permissions>
<privapp-permissions package="com.android.location.fused">
<permission name="android.permission.INSTALL_LOCATION_PROVIDER"/>
</privapp-permissions>
<privapp-permissions package="com.android.managedprovisioning">
<permission name="android.permission.CHANGE_COMPONENT_ENABLED_STATE"/>
<permission name="android.permission.CHANGE_CONFIGURATION"/>
<permission name="android.permission.CONNECTIVITY_INTERNAL"/>
<permission name="android.permission.CRYPT_KEEPER"/>
<permission name="android.permission.DELETE_PACKAGES"/>
<permission name="android.permission.INSTALL_PACKAGES"/>
<permission name="android.permission.INTERACT_ACROSS_USERS"/>
<permission name="android.permission.MANAGE_DEVICE_ADMINS"/>
<permission name="android.permission.MANAGE_USERS"/>
<permission name="android.permission.MASTER_CLEAR"/>
AndroidManifest.xml: Add new network permission for managed provisioning Adding a new permission for managed provisioning to access privileged network operations. Bug: 115980767 Test: Compiles Change-Id: I6375c119a7c5e13f1648803c7da5cebd6830d46c
2018-11-14 14:53:53 -08:00
<permission name="android.permission.NETWORK_MANAGED_PROVISIONING"/>
Control privileged permissions for priv-apps Added support for privapp-permissions config element. It allows to explicitly control what privileged permissions applications should be granted. Feature is controlled by ro.control_privapp_permissions property. Possible values: - 0/false, the feature is completely disabled - signature|privileged permissions are granted automatically without logging. *Default behavior* - 1/true, enforce that only whitelisted permissions are granted. Only devices with ro.control_privapp_permission=1 will pass CTS tests. Test: Manual Bug:31008485 Change-Id: I93a8c2782cc72b3953f32c237086d08d82ac0d5b
2016-11-09 14:32:27 -08:00
<permission name="android.permission.PERFORM_CDMA_PROVISIONING"/>
Allow ManagedProvisioning to access imei and serial number. Bug: 122721358 Test: manual Change-Id: I0d8f191f4f1bc1d8a87842db717af329681b012a
2019-01-28 18:32:27 +00:00
<permission name="android.permission.READ_PRIVILEGED_PHONE_STATE"/>
Control privileged permissions for priv-apps Added support for privapp-permissions config element. It allows to explicitly control what privileged permissions applications should be granted. Feature is controlled by ro.control_privapp_permissions property. Possible values: - 0/false, the feature is completely disabled - signature|privileged permissions are granted automatically without logging. *Default behavior* - 1/true, enforce that only whitelisted permissions are granted. Only devices with ro.control_privapp_permission=1 will pass CTS tests. Test: Manual Bug:31008485 Change-Id: I93a8c2782cc72b3953f32c237086d08d82ac0d5b
2016-11-09 14:32:27 -08:00
<permission name="android.permission.SET_TIME"/>
<permission name="android.permission.SET_TIME_ZONE"/>
<permission name="android.permission.SHUTDOWN"/>
<permission name="android.permission.WRITE_SECURE_SETTINGS"/>
</privapp-permissions>
<privapp-permissions package="com.android.mms.service">
<permission name="android.permission.BIND_CARRIER_MESSAGING_SERVICE"/>
<permission name="android.permission.BIND_CARRIER_SERVICES"/>
<permission name="android.permission.INTERACT_ACROSS_USERS"/>
</privapp-permissions>
<privapp-permissions package="com.android.mtp">
<permission name="android.permission.MANAGE_USB"/>
</privapp-permissions>
<privapp-permissions package="com.android.musicfx">
<permission name="android.permission.CHANGE_COMPONENT_ENABLED_STATE"/>
</privapp-permissions>
Add networkrecommendation permissions to privapp perms list. Bug: 34235587 Test: Flashed and checked logcat for crash. Change-Id: Ib35070ea87e23a3be8804eb3796e02c76a5628d0
2017-01-11 20:54:03 -08:00
<privapp-permissions package="com.android.networkrecommendation">
<permission name="android.permission.SCORE_NETWORKS"/>
<permission name="android.permission.SUBSTITUTE_NOTIFICATION_APP_NAME"/>
<permission name="android.permission.WRITE_SECURE_SETTINGS"/>
</privapp-permissions>
Updated platform privileged permissions Change-Id: I84e27ec023b20205bacb026e0a7cc32c12f67a7b Test: manual Bug: 33499917 Bug: 34128772
2017-01-05 18:45:06 -08:00
<privapp-permissions package="com.android.omadm.service">
<permission name="android.permission.CHANGE_CONFIGURATION"/>
<permission name="android.permission.CONNECTIVITY_INTERNAL"/>
[DMService]: Add CONNECTIVITY_USE_RESTRICTED_NETWORKS permission DMService has to use restricted network to do some upgrade form carrier process. So it needs add CONNECTIVITY_USE_RESTRICTED_NETWORKS permission since Android Q is limited preinstalled app permissions. Bug: 19610688 Test: atest frameworks/base/tests/net/java/android/net/ Change-Id: Ie06e73220b61a5bc09e648b49146c2b81707accc
2018-08-03 14:55:52 +08:00
<permission name="android.permission.CONNECTIVITY_USE_RESTRICTED_NETWORKS"/>
Updated platform privileged permissions Change-Id: I84e27ec023b20205bacb026e0a7cc32c12f67a7b Test: manual Bug: 33499917 Bug: 34128772
2017-01-05 18:45:06 -08:00
<permission name="android.permission.MODIFY_PHONE_STATE"/>
<permission name="android.permission.READ_PRIVILEGED_PHONE_STATE"/>
<permission name="android.permission.WRITE_APN_SETTINGS"/>
<permission name="android.permission.WRITE_SECURE_SETTINGS"/>
</privapp-permissions>
Control privileged permissions for priv-apps Added support for privapp-permissions config element. It allows to explicitly control what privileged permissions applications should be granted. Feature is controlled by ro.control_privapp_permissions property. Possible values: - 0/false, the feature is completely disabled - signature|privileged permissions are granted automatically without logging. *Default behavior* - 1/true, enforce that only whitelisted permissions are granted. Only devices with ro.control_privapp_permission=1 will pass CTS tests. Test: Manual Bug:31008485 Change-Id: I93a8c2782cc72b3953f32c237086d08d82ac0d5b
2016-11-09 14:32:27 -08:00
<privapp-permissions package="com.android.packageinstaller">
<permission name="android.permission.DELETE_PACKAGES"/>
<permission name="android.permission.INSTALL_PACKAGES"/>
Split PackageInstaller app into installation and permissions management The two components were mostly independant for a long time. Since I1e80a3f5e63d02b3859ecf74af21ca4c61f96874 the installation flow does not grant any permissions anymore and the last connection between these parts was broken. The new app "com.android.packageinstaller" in frameworks/base/packages/PackageInstaller will only handle (side load) package installtion and uninstallation. The exisiting app will be renamed to "com.android.permissioncontroller" and only handle permission granting and permission management. This change does only minimal cleanup cleanup. In particularly it does not move any files in the old permissions controller. This is to not disturb other features currently in development. This change set also updates the make files to install the two apps on the appropriate devices. Further the permisson policy xmls need to be updated to point to the right packages. Test: Installed + uninstalled packages Granted permissions + managed permissions GtsPackageInstallTestCases GtsNoPermissionTestCases GtsNoPermissionTestCases25 GtsPackageInstallerTapjackingTestCases GtsPackageUninstallTestCases Change-Id: I2d3796b837fc0049e712c82a990907f305c8febf
2018-07-25 12:12:30 -07:00
<permission name="android.permission.USE_RESERVED_DISK"/>
<permission name="android.permission.MANAGE_USERS"/>
<permission name="android.permission.UPDATE_APP_OPS_STATS"/>
Show app installed notification from PackageInstaller Bug: 111214100 Change-Id: If3f82bfac740f4f3cf8312f396943f2ebd447c12 Test: Notifications are showing correctly after new apps installed
2018-09-05 20:55:11 +01:00
<permission name="android.permission.SUBSTITUTE_NOTIFICATION_APP_NAME"/>
Checkbox for removing contributes files Apps might have contributed files. During uninstall the files are usually left on the system. To avoid filling up the storage we allow the user to delete the files during uninstall. Bug: 112002130 Test: Uninstalled an app that contributed files Change-Id: I7e71ed524055bdda91ce9e66f995540363ceb229
2018-12-10 17:02:35 -08:00
<permission name="android.permission.CLEAR_APP_USER_DATA"/>
fragileUserData-apps might keep data on uninstall If an app declares that is has flagile user data, all the user to choose to keep the app-data on uninstall. Test: Unistalled apps that set the new flag and app that did not. Verified that the KEEP_DATA flag was set when checkbox was clicked. Change-Id: I032fb21854352bbc175934ae5eb68a1430b1d403 Fixes: 117578306
2018-12-12 11:28:57 -08:00
<permission name="android.permission.PACKAGE_USAGE_STATS"/>
Split PackageInstaller app into installation and permissions management The two components were mostly independant for a long time. Since I1e80a3f5e63d02b3859ecf74af21ca4c61f96874 the installation flow does not grant any permissions anymore and the last connection between these parts was broken. The new app "com.android.packageinstaller" in frameworks/base/packages/PackageInstaller will only handle (side load) package installtion and uninstallation. The exisiting app will be renamed to "com.android.permissioncontroller" and only handle permission granting and permission management. This change does only minimal cleanup cleanup. In particularly it does not move any files in the old permissions controller. This is to not disturb other features currently in development. This change set also updates the make files to install the two apps on the appropriate devices. Further the permisson policy xmls need to be updated to point to the right packages. Test: Installed + uninstalled packages Granted permissions + managed permissions GtsPackageInstallTestCases GtsNoPermissionTestCases GtsNoPermissionTestCases25 GtsPackageInstallerTapjackingTestCases GtsPackageUninstallTestCases Change-Id: I2d3796b837fc0049e712c82a990907f305c8febf
2018-07-25 12:12:30 -07:00
</privapp-permissions>
<privapp-permissions package="com.android.permissioncontroller">
<permission name="android.permission.CLEAR_APP_CACHE"/>
Control privileged permissions for priv-apps Added support for privapp-permissions config element. It allows to explicitly control what privileged permissions applications should be granted. Feature is controlled by ro.control_privapp_permissions property. Possible values: - 0/false, the feature is completely disabled - signature|privileged permissions are granted automatically without logging. *Default behavior* - 1/true, enforce that only whitelisted permissions are granted. Only devices with ro.control_privapp_permission=1 will pass CTS tests. Test: Manual Bug:31008485 Change-Id: I93a8c2782cc72b3953f32c237086d08d82ac0d5b
2016-11-09 14:32:27 -08:00
<permission name="android.permission.MANAGE_USERS"/>
Updated platform privileged permissions Change-Id: I84e27ec023b20205bacb026e0a7cc32c12f67a7b Test: manual Bug: 33499917 Bug: 34128772
2017-01-05 18:45:06 -08:00
<permission name="android.permission.OBSERVE_GRANT_REVOKE_PERMISSIONS"/>
Add a new Intent for seeing permission usages This intent is used by the Permissions Hub. We also give PermissionController the GET_APP_OPS_STATS permission. Bug: 63532550 Test: Used the Permissions Hub. Change-Id: If1254f67c12fc5052d6ad5ff8260778a7c59dccc
2018-09-27 11:18:44 -07:00
<permission name="android.permission.GET_APP_OPS_STATS"/>
Control privileged permissions for priv-apps Added support for privapp-permissions config element. It allows to explicitly control what privileged permissions applications should be granted. Feature is controlled by ro.control_privapp_permissions property. Possible values: - 0/false, the feature is completely disabled - signature|privileged permissions are granted automatically without logging. *Default behavior* - 1/true, enforce that only whitelisted permissions are granted. Only devices with ro.control_privapp_permission=1 will pass CTS tests. Test: Manual Bug:31008485 Change-Id: I93a8c2782cc72b3953f32c237086d08d82ac0d5b
2016-11-09 14:32:27 -08:00
<permission name="android.permission.UPDATE_APP_OPS_STATS"/>
</privapp-permissions>
<privapp-permissions package="com.android.phone">
<permission name="android.permission.ACCESS_IMS_CALL_SERVICE"/>
<permission name="android.permission.BIND_CARRIER_MESSAGING_SERVICE"/>
<permission name="android.permission.BIND_CARRIER_SERVICES"/>
Add BIND_IMS_SERVICE to permissions whitelist Adds android.permission.BIND_IMS_SERVICE to the permissions whitelist xml file. Bug: 34813244 Test: Manual Change-Id: I7a7ad1a361c9d2dcc51769bc74a436878ad4adc5
2017-02-03 10:42:25 -08:00
<permission name="android.permission.BIND_IMS_SERVICE"/>
Renamed BIND_DATA_SERVICE to BIND_TELEPHONY_DATA_SERVICE Also grated the permission to the phone process. Test: Manual Bug: 64132030 Change-Id: I1fc82a4e8038b1b05b56dcfa43c0c94955967700
2018-02-02 10:40:11 -08:00
<permission name="android.permission.BIND_TELEPHONY_DATA_SERVICE"/>
Updated platform privileged permissions Change-Id: I84e27ec023b20205bacb026e0a7cc32c12f67a7b Test: manual Bug: 33499917 Bug: 34128772
2017-01-05 18:45:06 -08:00
<permission name="android.permission.BIND_VISUAL_VOICEMAIL_SERVICE"/>
Control privileged permissions for priv-apps Added support for privapp-permissions config element. It allows to explicitly control what privileged permissions applications should be granted. Feature is controlled by ro.control_privapp_permissions property. Possible values: - 0/false, the feature is completely disabled - signature|privileged permissions are granted automatically without logging. *Default behavior* - 1/true, enforce that only whitelisted permissions are granted. Only devices with ro.control_privapp_permission=1 will pass CTS tests. Test: Manual Bug:31008485 Change-Id: I93a8c2782cc72b3953f32c237086d08d82ac0d5b
2016-11-09 14:32:27 -08:00
<permission name="android.permission.CALL_PRIVILEGED"/>
<permission name="android.permission.CHANGE_COMPONENT_ENABLED_STATE"/>
<permission name="android.permission.CHANGE_CONFIGURATION"/>
<permission name="android.permission.CHANGE_DEVICE_IDLE_TEMP_WHITELIST"/>
<permission name="android.permission.CONNECTIVITY_INTERNAL"/>
Declare new com.android.phone permission in whitelist. Bug: 35948554 Test: Will verify T/H build Change-Id: I41773160aa6515983a15365905a2cbb6b13e10c6
2017-03-03 17:42:35 -08:00
<permission name="android.permission.CONTROL_INCALL_EXPERIENCE"/>
Control privileged permissions for priv-apps Added support for privapp-permissions config element. It allows to explicitly control what privileged permissions applications should be granted. Feature is controlled by ro.control_privapp_permissions property. Possible values: - 0/false, the feature is completely disabled - signature|privileged permissions are granted automatically without logging. *Default behavior* - 1/true, enforce that only whitelisted permissions are granted. Only devices with ro.control_privapp_permission=1 will pass CTS tests. Test: Manual Bug:31008485 Change-Id: I93a8c2782cc72b3953f32c237086d08d82ac0d5b
2016-11-09 14:32:27 -08:00
<permission name="android.permission.DUMP"/>
<permission name="android.permission.INTERACT_ACROSS_USERS"/>
<permission name="android.permission.LOCAL_MAC_ADDRESS"/>
<permission name="android.permission.MANAGE_USERS"/>
<permission name="android.permission.MODIFY_PHONE_STATE"/>
Check for location access on TelephonyRegistry When sending outbound callbacks on CELL_INFO and CELL_LOCATION, check to make sure that the user has authorized us and the receiving app to get information on their location. Bug: 69637693 Test: manual: telephony testapp Change-Id: Iacfc894428b11a7ec973567d7a797eedb281355f
2017-11-22 17:38:15 -08:00
<permission name="android.permission.PACKAGE_USAGE_STATS"/>
Control privileged permissions for priv-apps Added support for privapp-permissions config element. It allows to explicitly control what privileged permissions applications should be granted. Feature is controlled by ro.control_privapp_permissions property. Possible values: - 0/false, the feature is completely disabled - signature|privileged permissions are granted automatically without logging. *Default behavior* - 1/true, enforce that only whitelisted permissions are granted. Only devices with ro.control_privapp_permission=1 will pass CTS tests. Test: Manual Bug:31008485 Change-Id: I93a8c2782cc72b3953f32c237086d08d82ac0d5b
2016-11-09 14:32:27 -08:00
<permission name="android.permission.PERFORM_CDMA_PROVISIONING"/>
Adding "Mobile data" and "Data usage" button in mobile settings. Grant "READ_NETWORK_USAGE_HISTORY" permission to phone because "Datat usage" button summary needs it. Settings provides new intent to open mobile data usage page. Bug: 62201918 Test: Manual Change-Id: Ie317109c723f3946ace4d34c743081a7ae046462
2017-06-20 11:36:01 -07:00
<permission name="android.permission.READ_NETWORK_USAGE_HISTORY"/>
Control privileged permissions for priv-apps Added support for privapp-permissions config element. It allows to explicitly control what privileged permissions applications should be granted. Feature is controlled by ro.control_privapp_permissions property. Possible values: - 0/false, the feature is completely disabled - signature|privileged permissions are granted automatically without logging. *Default behavior* - 1/true, enforce that only whitelisted permissions are granted. Only devices with ro.control_privapp_permission=1 will pass CTS tests. Test: Manual Bug:31008485 Change-Id: I93a8c2782cc72b3953f32c237086d08d82ac0d5b
2016-11-09 14:32:27 -08:00
<permission name="android.permission.READ_PRIVILEGED_PHONE_STATE"/>
<permission name="android.permission.READ_SEARCH_INDEXABLES"/>
<permission name="android.permission.REBOOT"/>
<permission name="android.permission.REGISTER_CALL_PROVIDER"/>
<permission name="android.permission.REGISTER_SIM_SUBSCRIPTION"/>
<permission name="android.permission.SEND_RESPOND_VIA_MESSAGE"/>
<permission name="android.permission.SET_TIME"/>
<permission name="android.permission.SET_TIME_ZONE"/>
<permission name="android.permission.SHUTDOWN"/>
<permission name="android.permission.STATUS_BAR"/>
<permission name="android.permission.STOP_APP_SWITCHES"/>
<permission name="android.permission.UPDATE_APP_OPS_STATS"/>
<permission name="android.permission.UPDATE_DEVICE_STATS"/>
<permission name="android.permission.UPDATE_LOCK"/>
<permission name="android.permission.WRITE_APN_SETTINGS"/>
<permission name="android.permission.WRITE_SECURE_SETTINGS"/>
Public EuiccManager APIs. Public EuiccManager and other related necessary files. Mark EuiccCardManager and other related necessary files as @SystemApi. Solve lint errors and warnings. Bug: 35851809 Test: test on phone Change-Id: I68853e134e1e31fa9b91a83af6c491a2a8cca971
2017-12-12 20:17:09 -08:00
<permission name="android.permission.WRITE_EMBEDDED_SUBSCRIPTIONS"/>
Adding READ_PRECISE_CALL_STATE permission in phone app. This is needed if internal component wants to listen to precise call state change. Bug: 117980553 Test: unittest Change-Id: Id5a60519cbf1d724f939fc10b1f03cccfe5c1b5c
2019-01-22 13:46:17 -08:00
<permission name="android.permission.READ_PRECISE_PHONE_STATE"/>
Control privileged permissions for priv-apps Added support for privapp-permissions config element. It allows to explicitly control what privileged permissions applications should be granted. Feature is controlled by ro.control_privapp_permissions property. Possible values: - 0/false, the feature is completely disabled - signature|privileged permissions are granted automatically without logging. *Default behavior* - 1/true, enforce that only whitelisted permissions are granted. Only devices with ro.control_privapp_permission=1 will pass CTS tests. Test: Manual Bug:31008485 Change-Id: I93a8c2782cc72b3953f32c237086d08d82ac0d5b
2016-11-09 14:32:27 -08:00
<permission name="com.android.voicemail.permission.READ_VOICEMAIL"/>
<permission name="com.android.voicemail.permission.WRITE_VOICEMAIL"/>
</privapp-permissions>
<privapp-permissions package="com.android.providers.calendar">
<permission name="android.permission.GET_ACCOUNTS_PRIVILEGED"/>
Add extra permissions to CalendarProvider. Per requirement of cross profile calendar feature, CalendarProvider will need MANAGE_USER to get work profile user, and INTERACT_WITH_USER to access its work profile equivalent. Personal CalendarProvider needs to get the corp user ID, so it needs to call userManager.getUsers() which requires {@link android.Manifest.permission#MANAGE_USERS} permission. We'll maintain a whitelist of packages set by DPC that are granted access to cross profile Uris in CalendarProvider, so random personal apps won't be able to access those Uris. Bug: 118456304 Test: manual Change-Id: I59e4a7f39f9abc69f0dcc7ff03d822b8d44b4dbc
2018-10-26 18:52:37 +01:00
<permission name="android.permission.INTERACT_ACROSS_USERS" />
<permission name="android.permission.MANAGE_USERS" />
Control privileged permissions for priv-apps Added support for privapp-permissions config element. It allows to explicitly control what privileged permissions applications should be granted. Feature is controlled by ro.control_privapp_permissions property. Possible values: - 0/false, the feature is completely disabled - signature|privileged permissions are granted automatically without logging. *Default behavior* - 1/true, enforce that only whitelisted permissions are granted. Only devices with ro.control_privapp_permission=1 will pass CTS tests. Test: Manual Bug:31008485 Change-Id: I93a8c2782cc72b3953f32c237086d08d82ac0d5b
2016-11-09 14:32:27 -08:00
<permission name="android.permission.UPDATE_APP_OPS_STATS"/>
Start using new reserved disk GID. We recently created a new GID that can be granted to critical system processes, so that the system is usable enough for the user to free up disk space used by abusive apps. Define a permission for the GID so we can grant it to system apps, and add the GID to core apps needed for system stability. (The list was mostly derived from filling a disk and seeing what caused the device to fall over.) Test: builds, boots Bug: 62024591 Change-Id: Icdf471ed3bed4eeb8c01f1d39f0b40c1ea098396
2018-01-05 17:09:52 -07:00
<permission name="android.permission.USE_RESERVED_DISK"/>
Control privileged permissions for priv-apps Added support for privapp-permissions config element. It allows to explicitly control what privileged permissions applications should be granted. Feature is controlled by ro.control_privapp_permissions property. Possible values: - 0/false, the feature is completely disabled - signature|privileged permissions are granted automatically without logging. *Default behavior* - 1/true, enforce that only whitelisted permissions are granted. Only devices with ro.control_privapp_permission=1 will pass CTS tests. Test: Manual Bug:31008485 Change-Id: I93a8c2782cc72b3953f32c237086d08d82ac0d5b
2016-11-09 14:32:27 -08:00
</privapp-permissions>
<privapp-permissions package="com.android.providers.contacts">
<permission name="android.permission.BIND_DIRECTORY_SEARCH"/>
<permission name="android.permission.GET_ACCOUNTS_PRIVILEGED"/>
<permission name="android.permission.INTERACT_ACROSS_USERS"/>
<permission name="android.permission.MANAGE_USERS"/>
<permission name="android.permission.UPDATE_APP_OPS_STATS"/>
Start using new reserved disk GID. We recently created a new GID that can be granted to critical system processes, so that the system is usable enough for the user to free up disk space used by abusive apps. Define a permission for the GID so we can grant it to system apps, and add the GID to core apps needed for system stability. (The list was mostly derived from filling a disk and seeing what caused the device to fall over.) Test: builds, boots Bug: 62024591 Change-Id: Icdf471ed3bed4eeb8c01f1d39f0b40c1ea098396
2018-01-05 17:09:52 -07:00
<permission name="android.permission.USE_RESERVED_DISK"/>
Control privileged permissions for priv-apps Added support for privapp-permissions config element. It allows to explicitly control what privileged permissions applications should be granted. Feature is controlled by ro.control_privapp_permissions property. Possible values: - 0/false, the feature is completely disabled - signature|privileged permissions are granted automatically without logging. *Default behavior* - 1/true, enforce that only whitelisted permissions are granted. Only devices with ro.control_privapp_permission=1 will pass CTS tests. Test: Manual Bug:31008485 Change-Id: I93a8c2782cc72b3953f32c237086d08d82ac0d5b
2016-11-09 14:32:27 -08:00
</privapp-permissions>
<privapp-permissions package="com.android.providers.downloads">
<permission name="android.permission.ACCESS_CACHE_FILESYSTEM"/>
<permission name="android.permission.CLEAR_APP_CACHE"/>
<permission name="android.permission.CONNECTIVITY_INTERNAL"/>
<permission name="android.permission.UPDATE_APP_OPS_STATS"/>
<permission name="android.permission.UPDATE_DEVICE_STATS"/>
</privapp-permissions>
<privapp-permissions package="com.android.providers.media">
<permission name="android.permission.ACCESS_MTP"/>
<permission name="android.permission.INTERACT_ACROSS_USERS"/>
<permission name="android.permission.MANAGE_USERS"/>
Start using new reserved disk GID. We recently created a new GID that can be granted to critical system processes, so that the system is usable enough for the user to free up disk space used by abusive apps. Define a permission for the GID so we can grant it to system apps, and add the GID to core apps needed for system stability. (The list was mostly derived from filling a disk and seeing what caused the device to fall over.) Test: builds, boots Bug: 62024591 Change-Id: Icdf471ed3bed4eeb8c01f1d39f0b40c1ea098396
2018-01-05 17:09:52 -07:00
<permission name="android.permission.USE_RESERVED_DISK"/>
Control privileged permissions for priv-apps Added support for privapp-permissions config element. It allows to explicitly control what privileged permissions applications should be granted. Feature is controlled by ro.control_privapp_permissions property. Possible values: - 0/false, the feature is completely disabled - signature|privileged permissions are granted automatically without logging. *Default behavior* - 1/true, enforce that only whitelisted permissions are granted. Only devices with ro.control_privapp_permission=1 will pass CTS tests. Test: Manual Bug:31008485 Change-Id: I93a8c2782cc72b3953f32c237086d08d82ac0d5b
2016-11-09 14:32:27 -08:00
<permission name="android.permission.WRITE_MEDIA_STORAGE"/>
</privapp-permissions>
<privapp-permissions package="com.android.providers.telephony">
<permission name="android.permission.INTERACT_ACROSS_USERS"/>
<permission name="android.permission.MODIFY_PHONE_STATE"/>
Start using new reserved disk GID. We recently created a new GID that can be granted to critical system processes, so that the system is usable enough for the user to free up disk space used by abusive apps. Define a permission for the GID so we can grant it to system apps, and add the GID to core apps needed for system stability. (The list was mostly derived from filling a disk and seeing what caused the device to fall over.) Test: builds, boots Bug: 62024591 Change-Id: Icdf471ed3bed4eeb8c01f1d39f0b40c1ea098396
2018-01-05 17:09:52 -07:00
<permission name="android.permission.USE_RESERVED_DISK"/>
Control privileged permissions for priv-apps Added support for privapp-permissions config element. It allows to explicitly control what privileged permissions applications should be granted. Feature is controlled by ro.control_privapp_permissions property. Possible values: - 0/false, the feature is completely disabled - signature|privileged permissions are granted automatically without logging. *Default behavior* - 1/true, enforce that only whitelisted permissions are granted. Only devices with ro.control_privapp_permission=1 will pass CTS tests. Test: Manual Bug:31008485 Change-Id: I93a8c2782cc72b3953f32c237086d08d82ac0d5b
2016-11-09 14:32:27 -08:00
</privapp-permissions>
Add priv-app permissions for NetworkStack Bug: b/112869080 Test: m, flashed, booted Change-Id: Ia2cf0f708d815a5e5f49924fb15bb9c728f4ad56
2018-12-27 11:49:21 +09:00
<privapp-permissions package="com.android.mainline.networkstack">
<permission name="android.permission.ACCESS_NETWORK_CONDITIONS"/>
<permission name="android.permission.CHANGE_BACKGROUND_DATA_SETTING"/>
<permission name="android.permission.CONNECTIVITY_INTERNAL"/>
<permission name="android.permission.CONNECTIVITY_USE_RESTRICTED_NETWORKS"/>
<permission name="android.permission.CONTROL_VPN"/>
<permission name="android.permission.LOCAL_MAC_ADDRESS"/>
<permission name="android.permission.MANAGE_IPSEC_TUNNELS"/>
<permission name="android.permission.MANAGE_NETWORK_POLICY"/>
<permission name="android.permission.MANAGE_SUBSCRIPTION_PLANS"/>
<permission name="android.permission.MANAGE_USB"/>
<permission name="android.permission.NETWORK_BYPASS_PRIVATE_DNS"/>
<permission name="android.permission.NETWORK_SETTINGS"/>
<permission name="android.permission.NETWORK_STACK" />
<permission name="android.permission.NET_TUNNELING"/>
<permission name="android.permission.PACKET_KEEPALIVE_OFFLOAD"/>
<permission name="android.permission.PEERS_MAC_ADDRESS"/>
<permission name="android.permission.READ_NETWORK_USAGE_HISTORY"/>
<permission name="android.permission.READ_PRECISE_PHONE_STATE"/>
<permission name="android.permission.READ_PRIVILEGED_PHONE_STATE"/>
<permission name="android.permission.READ_WIFI_CREDENTIAL"/>
<permission name="android.permission.RECEIVE_DATA_ACTIVITY_CHANGE"/>
<permission name="android.permission.TETHER_PRIVILEGED"/>
<permission name="android.permission.WRITE_SECURE_SETTINGS"/>
</privapp-permissions>
Control privileged permissions for priv-apps Added support for privapp-permissions config element. It allows to explicitly control what privileged permissions applications should be granted. Feature is controlled by ro.control_privapp_permissions property. Possible values: - 0/false, the feature is completely disabled - signature|privileged permissions are granted automatically without logging. *Default behavior* - 1/true, enforce that only whitelisted permissions are granted. Only devices with ro.control_privapp_permission=1 will pass CTS tests. Test: Manual Bug:31008485 Change-Id: I93a8c2782cc72b3953f32c237086d08d82ac0d5b
2016-11-09 14:32:27 -08:00
<privapp-permissions package="com.android.server.telecom">
<permission name="android.permission.BIND_CONNECTION_SERVICE"/>
<permission name="android.permission.BIND_INCALL_SERVICE"/>
<permission name="android.permission.CALL_PRIVILEGED"/>
<permission name="android.permission.INTERACT_ACROSS_USERS"/>
<permission name="android.permission.MANAGE_USERS"/>
Add call recording tone support. Adding carrier configuration option to specify whether the carrier requires the incall recording tone be played. Added phone account extra used in Telephony to communicate this to Telecom. Added permission pregrant for Telecom for MODIFY_AUDIO_ROUTING; this is needed as Telecom listening to the AudioRecordingConfiguration callback from the audio framework. It needs the permission so that it can be informed of the package names of recording apps. Test: Manually enabled for local carrier and confirmed that recording tone plays to remote party when a recording app is started on the device. Bug: 64138141 Change-Id: I1ab521b79cbeeb4ff4dcbf83de7c17c539637bdc
2018-01-29 14:30:52 -08:00
<permission name="android.permission.MODIFY_AUDIO_ROUTING" />
Control privileged permissions for priv-apps Added support for privapp-permissions config element. It allows to explicitly control what privileged permissions applications should be granted. Feature is controlled by ro.control_privapp_permissions property. Possible values: - 0/false, the feature is completely disabled - signature|privileged permissions are granted automatically without logging. *Default behavior* - 1/true, enforce that only whitelisted permissions are granted. Only devices with ro.control_privapp_permission=1 will pass CTS tests. Test: Manual Bug:31008485 Change-Id: I93a8c2782cc72b3953f32c237086d08d82ac0d5b
2016-11-09 14:32:27 -08:00
<permission name="android.permission.MODIFY_PHONE_STATE"/>
<permission name="android.permission.STOP_APP_SWITCHES"/>
Add SUBSTITUTE_NOTIFICATION_APP_NAME pregrant for Telecom. Test: Manual Bug: 36817809 Change-Id: I2d7439e3d0040b617a842812b6ae8bda3c32f1ee
2017-03-31 17:50:56 -07:00
<permission name="android.permission.SUBSTITUTE_NOTIFICATION_APP_NAME"/>
Control privileged permissions for priv-apps Added support for privapp-permissions config element. It allows to explicitly control what privileged permissions applications should be granted. Feature is controlled by ro.control_privapp_permissions property. Possible values: - 0/false, the feature is completely disabled - signature|privileged permissions are granted automatically without logging. *Default behavior* - 1/true, enforce that only whitelisted permissions are granted. Only devices with ro.control_privapp_permission=1 will pass CTS tests. Test: Manual Bug:31008485 Change-Id: I93a8c2782cc72b3953f32c237086d08d82ac0d5b
2016-11-09 14:32:27 -08:00
</privapp-permissions>
<privapp-permissions package="com.android.sharedstoragebackup">
<permission name="android.permission.WRITE_MEDIA_STORAGE"/>
</privapp-permissions>
<privapp-permissions package="com.android.shell">
Crash if not all privileged permissions are whitelisted Test: reboot device - no crashes Test: Ran privapp_permissions.py for fugu/marlin/taimen Bug: 64693550 Change-Id: I9522ccaa75858b9a3d153c95c529eff70cd13994
2017-10-06 17:02:21 -07:00
<permission name="android.permission.ACCESS_LOWPAN_STATE"/>
Control privileged permissions for priv-apps Added support for privapp-permissions config element. It allows to explicitly control what privileged permissions applications should be granted. Feature is controlled by ro.control_privapp_permissions property. Possible values: - 0/false, the feature is completely disabled - signature|privileged permissions are granted automatically without logging. *Default behavior* - 1/true, enforce that only whitelisted permissions are granted. Only devices with ro.control_privapp_permission=1 will pass CTS tests. Test: Manual Bug:31008485 Change-Id: I93a8c2782cc72b3953f32c237086d08d82ac0d5b
2016-11-09 14:32:27 -08:00
<permission name="android.permission.BACKUP"/>
<permission name="android.permission.BATTERY_STATS"/>
<permission name="android.permission.BIND_APPWIDGET"/>
Make CHANGE_APP_IDLE_STATE a system API Allows a privileged app to set standby bucket states for apps. Bug: 63527785 Test: adb shell am set-standby-bucket com.example.foo 0 Change-Id: I613f8872ae816e39b167aad1c289187362aa6094
2017-10-31 13:29:00 -07:00
<permission name="android.permission.CHANGE_APP_IDLE_STATE"/>
Control privileged permissions for priv-apps Added support for privapp-permissions config element. It allows to explicitly control what privileged permissions applications should be granted. Feature is controlled by ro.control_privapp_permissions property. Possible values: - 0/false, the feature is completely disabled - signature|privileged permissions are granted automatically without logging. *Default behavior* - 1/true, enforce that only whitelisted permissions are granted. Only devices with ro.control_privapp_permission=1 will pass CTS tests. Test: Manual Bug:31008485 Change-Id: I93a8c2782cc72b3953f32c237086d08d82ac0d5b
2016-11-09 14:32:27 -08:00
<permission name="android.permission.CHANGE_COMPONENT_ENABLED_STATE"/>
<permission name="android.permission.CHANGE_CONFIGURATION"/>
Give shell the CHANGE_DEVICE_IDLE_TEMP_WHITELIST permission Shell needs to have this permission in order for the deviceidle tempwhitelist shell command to exist. Bug 34715096 Test: cts-tradefed run cts -m CtsAppTestCases \ -t android.app.cts.ActivityManagerTest#testBackgroundCheckService Change-Id: Ic1fdd87b6020649705ba0c9349dd00dd096037f3
2017-03-21 17:43:47 -07:00
<permission name="android.permission.CHANGE_DEVICE_IDLE_TEMP_WHITELIST" />
Crash if not all privileged permissions are whitelisted Test: reboot device - no crashes Test: Ran privapp_permissions.py for fugu/marlin/taimen Bug: 64693550 Change-Id: I9522ccaa75858b9a3d153c95c529eff70cd13994
2017-10-06 17:02:21 -07:00
<permission name="android.permission.CHANGE_LOWPAN_STATE"/>
Whitelist new CHANGE_OVERLAY_PACKAGES permission The Shell application needs access to change which overlays are enabled in OverlayManagerService. Test: Manual: invoke adb exec-out cmd overlay enable some.package.name when shell is not root (adb unroot on eng builds). Change-Id: I1849f68e244cfc9b1e13eb0e673dde7be03cba6d
2017-02-23 18:17:11 -08:00
<permission name="android.permission.CHANGE_OVERLAY_PACKAGES"/>
Grant Shell ability to clear cached app data. It already has CLEAR_APP_USER_DATA to clear everything inside app storage, and clearing cached data is a subset of that. Test: cts-tradefed run commandAndExit cts-dev -m CtsAppSecurityHostTestCases -t android.appsecurity.cts.StorageHostTest Bug: 36731175 Change-Id: Iefc5be6c80e2562a95424fd6fe413bdb018201a9
2017-04-09 21:37:56 -06:00
<permission name="android.permission.CLEAR_APP_CACHE"/>
Control privileged permissions for priv-apps Added support for privapp-permissions config element. It allows to explicitly control what privileged permissions applications should be granted. Feature is controlled by ro.control_privapp_permissions property. Possible values: - 0/false, the feature is completely disabled - signature|privileged permissions are granted automatically without logging. *Default behavior* - 1/true, enforce that only whitelisted permissions are granted. Only devices with ro.control_privapp_permission=1 will pass CTS tests. Test: Manual Bug:31008485 Change-Id: I93a8c2782cc72b3953f32c237086d08d82ac0d5b
2016-11-09 14:32:27 -08:00
<permission name="android.permission.CONNECTIVITY_INTERNAL"/>
<permission name="android.permission.DELETE_CACHE_FILES"/>
<permission name="android.permission.DELETE_PACKAGES"/>
<permission name="android.permission.DUMP"/>
DO NOT MERGE Add permission to launch activities on VD 1. Added permission ACTIVITY_EMBEDDING which allows apps to launch activities on virtual displays. 2. Allow owner of display to launch activities from same app without permission check to owned display. 3. Added permission checks for launching on secondary displays to more target task/stack resolution paths in ActivityStarter. Bug: 63117330 Test: android.server.cts.ActivityManagerDisplayTests Test: go/wm-smoke Change-Id: If169a77fb56241e06f7de20168dc38c4b0a217f5 (cherry picked from commit 71587649836d8e97c2ca00d968fc95293b59b0d3)
2017-07-06 14:28:59 -07:00
<permission name="android.permission.ACTIVITY_EMBEDDING"/>
Control privileged permissions for priv-apps Added support for privapp-permissions config element. It allows to explicitly control what privileged permissions applications should be granted. Feature is controlled by ro.control_privapp_permissions property. Possible values: - 0/false, the feature is completely disabled - signature|privileged permissions are granted automatically without logging. *Default behavior* - 1/true, enforce that only whitelisted permissions are granted. Only devices with ro.control_privapp_permission=1 will pass CTS tests. Test: Manual Bug:31008485 Change-Id: I93a8c2782cc72b3953f32c237086d08d82ac0d5b
2016-11-09 14:32:27 -08:00
<permission name="android.permission.FORCE_STOP_PACKAGES"/>
<permission name="android.permission.GET_APP_OPS_STATS"/>
<permission name="android.permission.INSTALL_LOCATION_PROVIDER"/>
<permission name="android.permission.INSTALL_PACKAGES"/>
<permission name="android.permission.INTERACT_ACROSS_USERS"/>
Restrict access from apps to bluetooth_address setting BluetoothManagerService for some reason leaks the Android's Bluetooth MAC address via Settings.Secure which is normally readable by all apps. This lets apps bypass the restriction on access to Bluetooth MAC address from apps. This commit fixes the issue by restricting access to bluetooth_address secure setting (Settings.Secure). Only packages which hold the android.permission.LOCAL_MAC_ADDRESS permission retain access. This commit accordingly grants LOCAL_MAC_ADDRESS permission to the system Shell app because a number of scripts (including Android CTS) use "adb shell settings get secure bluetooth_address" as a convenient way to query the device's Bluetooth MAC address over ADB. This is acceptable because the user of the device can see the Bluetooth MAC address and thus it's fine for shell to be able to see the address as well. Test: See CTS test added in the cts project in this topic. Test: "adb shell settings get secure bluetooth_address" returns the Bluetooth MAC address of the Android. Test: "adb shell settings list secure | grep bluetooth_address" returns the Bluetooth MAC address of the Android. Test: Bluetooth works (toggling off/on, pairing, file transfer) Bug: 33701414 Change-Id: I17b110b96eb3794b25c1661e93d29a7a003e3c9a
2017-03-03 14:08:36 -08:00
<permission name="android.permission.LOCAL_MAC_ADDRESS"/>
Make performAccessibilityShortcut a SystemAPI Also create a new MANAGE_ACCESSIBILITY permission to perform the shortcut. Bug: 116118615 Test: make, activate accessibility shortcut Change-Id: Ic65a0cdf7393429e14cb98f4fb0734d20069b05a
2018-10-09 15:01:49 -07:00
<permission name="android.permission.MANAGE_ACCESSIBILITY"/>
Control privileged permissions for priv-apps Added support for privapp-permissions config element. It allows to explicitly control what privileged permissions applications should be granted. Feature is controlled by ro.control_privapp_permissions property. Possible values: - 0/false, the feature is completely disabled - signature|privileged permissions are granted automatically without logging. *Default behavior* - 1/true, enforce that only whitelisted permissions are granted. Only devices with ro.control_privapp_permission=1 will pass CTS tests. Test: Manual Bug:31008485 Change-Id: I93a8c2782cc72b3953f32c237086d08d82ac0d5b
2016-11-09 14:32:27 -08:00
<permission name="android.permission.MANAGE_DEVICE_ADMINS"/>
Allow the shell to set USB functions. Bug: 25596495 Test: svc usb setFunction mtp true Change-Id: I4472464a1c7ed100cb257dbad83d1d8cfef88fc7
2017-02-17 11:46:58 -08:00
<permission name="android.permission.MANAGE_USB"/>
Control privileged permissions for priv-apps Added support for privapp-permissions config element. It allows to explicitly control what privileged permissions applications should be granted. Feature is controlled by ro.control_privapp_permissions property. Possible values: - 0/false, the feature is completely disabled - signature|privileged permissions are granted automatically without logging. *Default behavior* - 1/true, enforce that only whitelisted permissions are granted. Only devices with ro.control_privapp_permission=1 will pass CTS tests. Test: Manual Bug:31008485 Change-Id: I93a8c2782cc72b3953f32c237086d08d82ac0d5b
2016-11-09 14:32:27 -08:00
<permission name="android.permission.MODIFY_APPWIDGET_BIND_PERMISSIONS"/>
<permission name="android.permission.MODIFY_PHONE_STATE"/>
<permission name="android.permission.MOUNT_FORMAT_FILESYSTEMS"/>
<permission name="android.permission.MOUNT_UNMOUNT_FILESYSTEMS"/>
<permission name="android.permission.MOVE_PACKAGE"/>
Add PACKAGE_USAGE_STATS permission to shell. This is needed for calling AM.registerUidObserver. Fixes: 64400666 Test: cts-tradefed run singleCommand cts-dev -m CtsAppTestCases -t \ android.app.cts.ActivityManagerProcessStateTest Change-Id: I4f500d0d8d516b6b8961ea2f8c083add3ae949a9
2017-09-01 16:41:10 -07:00
<permission name="android.permission.PACKAGE_USAGE_STATS" />
Create APIs to interact with DynamicPowerSaver This creates the PowerManager APIs that allow apps with the appropriate permissions to interact with Dynamic Power Saver. Bug: 111450127 Test: WIP Change-Id: I5b9483fa0fba81a4ade622b1f3dbaec580b68a67
2018-10-19 13:03:20 -07:00
<permission name="android.permission.POWER_SAVER" />
Control privileged permissions for priv-apps Added support for privapp-permissions config element. It allows to explicitly control what privileged permissions applications should be granted. Feature is controlled by ro.control_privapp_permissions property. Possible values: - 0/false, the feature is completely disabled - signature|privileged permissions are granted automatically without logging. *Default behavior* - 1/true, enforce that only whitelisted permissions are granted. Only devices with ro.control_privapp_permission=1 will pass CTS tests. Test: Manual Bug:31008485 Change-Id: I93a8c2782cc72b3953f32c237086d08d82ac0d5b
2016-11-09 14:32:27 -08:00
<permission name="android.permission.READ_FRAME_BUFFER"/>
Crash if not all privileged permissions are whitelisted Test: reboot device - no crashes Test: Ran privapp_permissions.py for fugu/marlin/taimen Bug: 64693550 Change-Id: I9522ccaa75858b9a3d153c95c529eff70cd13994
2017-10-06 17:02:21 -07:00
<permission name="android.permission.READ_LOWPAN_CREDENTIAL"/>
new SystemAPI for preciseCallState and DisconnectCause 1. decouple disconnectCause and preciseDisconnectCuase from preciseCallState. 2. expose preciseCallState to SystemAPI and expose onPreciseCallStateChanged to System API 3. remove/hide ImsReasonInfo from PreciseDisconnectCuase 4. expose DiconnectCuase and PreciseDisconnectCause to System API 5. new onDisconnectCauseChanged API on PhoneStateListener for CS call and use ImsCallSessionListener for IMS call(imsreasonInfo) 6. add read_precise_phone_state to shell apk to enable GTS test Bug: 119890559 Test: atest GtsGmscoreHostTestCases:TelephonyHostTest#testPhoneStateListener Change-Id: If9256feff16b6bcaef1dfe194c2b0df2a48436b0
2018-12-12 19:59:30 -08:00
<!-- Needed for test only -->
<permission name="android.permission.READ_PRECISE_PHONE_STATE" />
Protect Device Identifiers behind priv permission and DO/PO checks Bug: 110099294 Test: cts-tradefed run cts -m CtsDevicePolicyManagerTestCases \ -t com.android.cts.devicepolicy.DeviceOwnerTest.testDeviceOwnerCanGetDeviceIdentifiers Test: cts-tradefed run cts -m CtsDevicePolicyManagerTestCases \ -t com.android.cts.devicepolicy.ManagedProfileTest#testGetDeviceIdentifiers Test: cts-tradefed run cts -m CtsTelephonyTestCases -t android.telephony.cts.TelephonyManagerTest Test: cts-tradefed run cts -m CtsPermissionTestCases -t android.permission.cts.TelephonyManagerPermissionTest Change-Id: I3c82c53ec89cd17b34a61166ccc9e9747388efac
2018-10-01 16:14:50 -07:00
<permission name="android.permission.READ_PRIVILEGED_PHONE_STATE"/>
Control privileged permissions for priv-apps Added support for privapp-permissions config element. It allows to explicitly control what privileged permissions applications should be granted. Feature is controlled by ro.control_privapp_permissions property. Possible values: - 0/false, the feature is completely disabled - signature|privileged permissions are granted automatically without logging. *Default behavior* - 1/true, enforce that only whitelisted permissions are granted. Only devices with ro.control_privapp_permission=1 will pass CTS tests. Test: Manual Bug:31008485 Change-Id: I93a8c2782cc72b3953f32c237086d08d82ac0d5b
2016-11-09 14:32:27 -08:00
<permission name="android.permission.REAL_GET_TASKS"/>
Add READ_PRIVILEGED_PHONE_STATE to used permissions Bug: 110099294 Test: cts-tradefed run cts -m CtsTelephonyTestCases -t android.telephony.cts.TelephonyManagerTest Change-Id: I13fec3d397c200ce92883883c96c07007e823efe
2018-10-08 09:39:24 -07:00
<permission name="android.permission.READ_PRIVILEGED_PHONE_STATE"/>
Control privileged permissions for priv-apps Added support for privapp-permissions config element. It allows to explicitly control what privileged permissions applications should be granted. Feature is controlled by ro.control_privapp_permissions property. Possible values: - 0/false, the feature is completely disabled - signature|privileged permissions are granted automatically without logging. *Default behavior* - 1/true, enforce that only whitelisted permissions are granted. Only devices with ro.control_privapp_permission=1 will pass CTS tests. Test: Manual Bug:31008485 Change-Id: I93a8c2782cc72b3953f32c237086d08d82ac0d5b
2016-11-09 14:32:27 -08:00
<permission name="android.permission.REGISTER_CALL_PROVIDER"/>
<permission name="android.permission.REGISTER_CONNECTION_MANAGER"/>
<permission name="android.permission.REGISTER_SIM_SUBSCRIPTION"/>
<permission name="android.permission.RETRIEVE_WINDOW_CONTENT"/>
<permission name="android.permission.SET_ALWAYS_FINISH"/>
<permission name="android.permission.SET_ANIMATION_SCALE"/>
<permission name="android.permission.SET_DEBUG_APP"/>
<permission name="android.permission.SET_PROCESS_LIMIT"/>
Add set-time and set-timezone shell cmds to alarm service These commands allow a user to set the time and the timezone from the shell. The shell now has signature|privileged SET_TIME and SET_TIME_ZONE permissions. Bug: 67751701 Test: manual - correctly sets the time and timezone from unrooted adb. Change-Id: I1d2820fd7dadd8b1f3900c0592eb28210370ce88
2018-02-01 10:13:10 -08:00
<permission name="android.permission.SET_TIME"/>
<permission name="android.permission.SET_TIME_ZONE"/>
Control privileged permissions for priv-apps Added support for privapp-permissions config element. It allows to explicitly control what privileged permissions applications should be granted. Feature is controlled by ro.control_privapp_permissions property. Possible values: - 0/false, the feature is completely disabled - signature|privileged permissions are granted automatically without logging. *Default behavior* - 1/true, enforce that only whitelisted permissions are granted. Only devices with ro.control_privapp_permission=1 will pass CTS tests. Test: Manual Bug:31008485 Change-Id: I93a8c2782cc72b3953f32c237086d08d82ac0d5b
2016-11-09 14:32:27 -08:00
<permission name="android.permission.SIGNAL_PERSISTENT_PROCESSES"/>
Add a new START_ACTIVITIES_FROM_BACKGROUND signature|privileged|vendorPrivileged|oem permission And grant it to SystemUI and Shell (adb shell am start). Bug: 110956953 Test: atest WmTests:ActivityStarterTests Change-Id: I4885a9a62ee8d47a3aef85f0e34b746c3f51ca2b
2018-12-14 15:17:29 +00:00
<permission name="android.permission.START_ACTIVITIES_FROM_BACKGROUND" />
Allow the shell to start task overlay activities. - Fix issue with testFinishPipActivityWithTaskOverlay failing due to new permission check in the system Bug: 71716434 Test: atest CtsActivityManagerDeviceTestCases:ActivityManagerPinnedStackTests#testFinishPipActivityWithTaskOverlay Change-Id: Ifbcd6c182d928f5aa5372d2db9fa71a142dc8474
2018-03-17 12:51:14 -07:00
<permission name="android.permission.START_TASKS_FROM_RECENTS" />
Control privileged permissions for priv-apps Added support for privapp-permissions config element. It allows to explicitly control what privileged permissions applications should be granted. Feature is controlled by ro.control_privapp_permissions property. Possible values: - 0/false, the feature is completely disabled - signature|privileged permissions are granted automatically without logging. *Default behavior* - 1/true, enforce that only whitelisted permissions are granted. Only devices with ro.control_privapp_permission=1 will pass CTS tests. Test: Manual Bug:31008485 Change-Id: I93a8c2782cc72b3953f32c237086d08d82ac0d5b
2016-11-09 14:32:27 -08:00
<permission name="android.permission.STOP_APP_SWITCHES"/>
<permission name="android.permission.SUBSTITUTE_NOTIFICATION_APP_NAME"/>
Add SUSPEND_APPS permission to shell Since this permission protects system apis, this is required for instrumentation tests. Test: atest com.google.android.suspendapps.gts.SuspendPackagesTest Bug: 79773970 Change-Id: Ib283018c50cc19c3958bd61e2d19befbf2805cc5
2018-07-16 13:23:21 -07:00
<permission name="android.permission.SUSPEND_APPS" />
Control privileged permissions for priv-apps Added support for privapp-permissions config element. It allows to explicitly control what privileged permissions applications should be granted. Feature is controlled by ro.control_privapp_permissions property. Possible values: - 0/false, the feature is completely disabled - signature|privileged permissions are granted automatically without logging. *Default behavior* - 1/true, enforce that only whitelisted permissions are granted. Only devices with ro.control_privapp_permission=1 will pass CTS tests. Test: Manual Bug:31008485 Change-Id: I93a8c2782cc72b3953f32c237086d08d82ac0d5b
2016-11-09 14:32:27 -08:00
<permission name="android.permission.UPDATE_APP_OPS_STATS"/>
Start using new reserved disk GID. We recently created a new GID that can be granted to critical system processes, so that the system is usable enough for the user to free up disk space used by abusive apps. Define a permission for the GID so we can grant it to system apps, and add the GID to core apps needed for system stability. (The list was mostly derived from filling a disk and seeing what caused the device to fall over.) Test: builds, boots Bug: 62024591 Change-Id: Icdf471ed3bed4eeb8c01f1d39f0b40c1ea098396
2018-01-05 17:09:52 -07:00
<permission name="android.permission.USE_RESERVED_DISK"/>
Control privileged permissions for priv-apps Added support for privapp-permissions config element. It allows to explicitly control what privileged permissions applications should be granted. Feature is controlled by ro.control_privapp_permissions property. Possible values: - 0/false, the feature is completely disabled - signature|privileged permissions are granted automatically without logging. *Default behavior* - 1/true, enforce that only whitelisted permissions are granted. Only devices with ro.control_privapp_permission=1 will pass CTS tests. Test: Manual Bug:31008485 Change-Id: I93a8c2782cc72b3953f32c237086d08d82ac0d5b
2016-11-09 14:32:27 -08:00
<permission name="android.permission.WRITE_MEDIA_STORAGE"/>
<permission name="android.permission.WRITE_SECURE_SETTINGS"/>
</privapp-permissions>
<privapp-permissions package="com.android.statementservice">
<permission name="android.permission.INTENT_FILTER_VERIFICATION_AGENT"/>
</privapp-permissions>
Declare privileged permissions of Live TV app Test: build Bug: 35782070 Change-Id: Ia1e39dcf8fdd3345837ebec1729ad4d02699763b
2017-03-20 15:19:11 -07:00
<privapp-permissions package="com.android.tv">
Add permissions for LiveTv (AOSP) It crashes without the permissions Bug: 67474061 Test: make; flashall; install and open LiveTv; Change-Id: Ifec8bfb4ee93ac6b9189a9c337fdd2ef9ec34537
2017-10-05 18:31:00 -07:00
<permission name="android.permission.CHANGE_HDMI_CEC_ACTIVE_SOURCE"/>
<permission name="android.permission.DVB_DEVICE"/>
<permission name="android.permission.GLOBAL_SEARCH"/>
<permission name="android.permission.HDMI_CEC"/>
<permission name="android.permission.MODIFY_PARENTAL_CONTROLS"/>
<permission name="android.permission.READ_CONTENT_RATING_SYSTEMS"/>
<permission name="com.android.providers.tv.permission.ACCESS_ALL_EPG_DATA"/>
<permission name="com.android.providers.tv.permission.ACCESS_WATCHED_PROGRAMS"/>
Declare privileged permissions of Live TV app Test: build Bug: 35782070 Change-Id: Ia1e39dcf8fdd3345837ebec1729ad4d02699763b
2017-03-20 15:19:11 -07:00
</privapp-permissions>
Control privileged permissions for priv-apps Added support for privapp-permissions config element. It allows to explicitly control what privileged permissions applications should be granted. Feature is controlled by ro.control_privapp_permissions property. Possible values: - 0/false, the feature is completely disabled - signature|privileged permissions are granted automatically without logging. *Default behavior* - 1/true, enforce that only whitelisted permissions are granted. Only devices with ro.control_privapp_permission=1 will pass CTS tests. Test: Manual Bug:31008485 Change-Id: I93a8c2782cc72b3953f32c237086d08d82ac0d5b
2016-11-09 14:32:27 -08:00
<privapp-permissions package="com.android.vpndialogs">
<permission name="android.permission.CONNECTIVITY_INTERNAL"/>
<permission name="android.permission.CONTROL_VPN"/>
</privapp-permissions>
Add BIND_IMS_SERVICE to permissions whitelist Adds android.permission.BIND_IMS_SERVICE to the permissions whitelist xml file. Bug: 34813244 Test: Manual Change-Id: I7a7ad1a361c9d2dcc51769bc74a436878ad4adc5
2017-02-03 10:42:25 -08:00
</permissions>
Reference in New Issue Copy Permalink