platform_system_sepolicy/public/charger.te

type charger, charger_type, domain;
type charger_exec, system_file_type, exec_type, file_type;

# The system charger is a client of HIDL health HAL.
hal_client_domain(charger, hal_health)
Add charger_type. This is the common type for domains that executes charger's functionalities, including setting and getting necessary properties, permissions to maintain the health loop, writing to kernel log, handling inputs and drawing screens, etc. Permissions specific to the system charger is not moved. Also enforce stricter neverallow rules on charger_{status,config}_prop. For charger_config_prop, only init / vendor_init can set. For charger_status_prop, only init / vendor_init / charger / health HAL can set. For both, only init / vendor_init / charger / dumpstate / health HAL can get. (Health HAL is determined by the intersection of charger_type and hal_health_server.) A follow up CL will be added to add charger_type to hal_health_default, the default domain for health HAL servers. Vendors may add charger_type to their domains that serves the health AIDL HAL as well. Test: manual Bug: 203246116 Change-Id: I0e99b6b68d381b7f73306d93ee4f8c5c8abdf026 2021-10-26 02:58:04 +02:00			`type charger, charger_type, domain;`
Move /sbin/charger to /system/bin/charger. With the CLs in the same topic, it's being built as a dynamically linked executable. And this applies to normal boot (including charger mode) and recovery mode both. /system/bin/charger under normal boot will be labeled as charger_exec, which has the attribute of system_file_type. The file in recovery image will still be labeled as rootfs. So we keep the domain_trans rule for rootfs file, but allowing for recovery mode only. Bug: 73660730 Test: Boot into charger mode on taimen. Check that charger UI works. Test: Boot into recovery mode. Check that charger process works. Change-Id: I062d81c346578cdfce1cc2dce18c829387a1fdbc 2018-09-08 00:05:33 +02:00			`type charger_exec, system_file_type, exec_type, file_type;`
healthd: create SEPolicy for 'charger' and reduce healthd's scope healthd is being split into 'charger' and 'healthd' processes, that will never run together. 'charger' is to be run only in charge-only and recovery, while healthd runs with Android. While they both share much of battery monitoring code, they both now have reduced scope. E.g. 'charger', doesn't need to use binder anymore and healthd doesn't need to do charging ui animation. So, amend the SEPolicy for healthd to reduce it's scope and add a new one for charger. Test: Tested all modes {recovery, charger-only, android} with new policy Change-Id: If7f81875c605f7f07da4d23a313f308b9dde9ce8 Signed-off-by: Sandeep Patil <sspatil@google.com> 2016-11-01 21:49:10 +01:00
Add charger_type. This is the common type for domains that executes charger's functionalities, including setting and getting necessary properties, permissions to maintain the health loop, writing to kernel log, handling inputs and drawing screens, etc. Permissions specific to the system charger is not moved. Also enforce stricter neverallow rules on charger_{status,config}_prop. For charger_config_prop, only init / vendor_init can set. For charger_status_prop, only init / vendor_init / charger / health HAL can set. For both, only init / vendor_init / charger / dumpstate / health HAL can get. (Health HAL is determined by the intersection of charger_type and hal_health_server.) A follow up CL will be added to add charger_type to hal_health_default, the default domain for health HAL servers. Vendors may add charger_type to their domains that serves the health AIDL HAL as well. Test: manual Bug: 203246116 Change-Id: I0e99b6b68d381b7f73306d93ee4f8c5c8abdf026 2021-10-26 02:58:04 +02:00			`# The system charger is a client of HIDL health HAL.`
Allow charger to open health passthrough HAL Test: charger mode Bug: 142286265 Change-Id: I75910cec415595ac9b503358ac4984ef478e44ad 2019-10-12 03:12:09 +02:00			`hal_client_domain(charger, hal_health)`