7f4a8a7291
Bug: 17471434 Change-Id: I6fd1079be29a454f46ab84f0c43fcf816e679c98
32 lines
982 B
Text
32 lines
982 B
Text
###
|
|
### Services with isolatedProcess=true in their manifest.
|
|
###
|
|
### This file defines the rules for isolated apps. An "isolated
|
|
### app" is an APP with UID between AID_ISOLATED_START (99000)
|
|
### and AID_ISOLATED_END (99999).
|
|
###
|
|
### isolated_app includes all the appdomain rules, plus the
|
|
### additional following rules:
|
|
###
|
|
|
|
type isolated_app, domain;
|
|
app_domain(isolated_app)
|
|
net_domain(isolated_app)
|
|
|
|
# Isolated apps shouldn't be able to access the driver directly.
|
|
neverallow isolated_app gpu_device:file { rw_file_perms execute };
|
|
|
|
# read and write access to app_data_file is already
|
|
# granted via app.te. Allow execute.
|
|
# Needed to allow dlopen() from Chrome renderer processes.
|
|
# See b/15902433 for details.
|
|
allow isolated_app app_data_file:file execute;
|
|
|
|
# Audited locally.
|
|
service_manager_local_audit_domain(isolated_app)
|
|
auditallow isolated_app {
|
|
service_manager_type
|
|
-radio_service
|
|
-surfaceflinger_service
|
|
-system_server_service
|
|
}:service_manager find;
|