blob: acbd84eb06caa8e2222d73e9a123c81fda56c5cc [file] [log] [blame]
Tom Cherry63492cd2017-11-15 14:57:14 -08001# Creating files on sysfs is impossible so this isn't a threat
2# Sometimes we have to write to non-existent files to avoid conditional
3# init behavior. See b/35303861 for an example.
4dontaudit vendor_init sysfs:dir write;
Paul Crowleyaed0f762019-08-01 15:57:47 -07005
6# TODO(b/140259336) We want to remove vendor_init in the long term but allow for now
7allow vendor_init system_data_root_file:dir rw_dir_perms;
Josh Gao0cac6fd2020-10-28 13:56:23 -07008
9# Let vendor_init set service.adb.tcp.port.
10set_prop(vendor_init, adbd_config_prop)
Andrew Walbrana995e842021-03-29 17:19:12 +000011
Andrew Scullaedd65a2021-10-08 12:13:46 +000012# Let vendor_init react to AVF device config changes
13get_prop(vendor_init, device_config_virtualization_framework_native_prop)
14
Jooyung Hancae23682022-09-02 16:26:27 +090015# Let vendor_init use apex.<name>.ready to start services from vendor APEX
16get_prop(vendor_init, apex_ready_prop)
17
Andrew Walbrana995e842021-03-29 17:19:12 +000018# chown/chmod on devices, e.g. /dev/ttyHS0
19allow vendor_init {
20 dev_type
21 -keychord_device
22 -kvm_device
23 -port_device
24 -lowpan_device
25 -hw_random_device
26}:chr_file setattr;