3ea47b9249
hwservicemanager can check hwservice_contexts files both from the framework and vendor partitions. Initially, have a wildcard '*' in hwservice_contexts that maps to a label that can be added/found from domain. This needs to be removed when the proper policy is in place. Also, grant su/shell access to hwservicemanager list operations, so tools like 'lshal' continue to work. Bug: 34454312 Test: Marlin boots Change-Id: I3a02d97a82458692b528d85c1b8e78b6f82ea1bc
22 lines
834 B
Text
22 lines
834 B
Text
# hwservicemanager - the Binder context manager for HAL services
|
|
type hwservicemanager, domain, mlstrustedsubject;
|
|
type hwservicemanager_exec, exec_type, file_type;
|
|
|
|
# Note that we do not use the binder_* macros here.
|
|
# hwservicemanager provides name service (aka context manager)
|
|
# for hwbinder.
|
|
# Additionally, it initiates binder IPC calls to
|
|
# clients who request service notifications. The permission
|
|
# to do this is granted in the hwbinder_use macro.
|
|
allow hwservicemanager self:binder set_context_mgr;
|
|
|
|
set_prop(hwservicemanager, hwservicemanager_prop)
|
|
|
|
# Scan through /system/lib64/hw looking for installed HALs
|
|
allow hwservicemanager system_file:dir r_dir_perms;
|
|
|
|
# Read hwservice_contexts
|
|
allow hwservicemanager hwservice_contexts_file:file r_file_perms;
|
|
|
|
# Check SELinux permissions.
|
|
selinux_check_access(hwservicemanager)
|