platform_system_sepolicy/vendor/hal_sensors_default.te

type hal_sensors_default, domain;
hal_server_domain(hal_sensors_default, hal_sensors)

type hal_sensors_default_exec, exec_type, vendor_file_type, file_type;
init_daemon_domain(hal_sensors_default)

allow hal_sensors_default fwk_scheduler_hwservice:hwservice_manager find;

allow hal_sensors_default input_device:dir r_dir_perms;
allow hal_sensors_default input_device:chr_file r_file_perms;

# Allow sensor hals to access and use gralloc memory allocated by
# android.hardware.graphics.allocator
allow hal_sensors_default hal_graphics_allocator_default:fd use;
allow hal_sensors_default ion_device:chr_file r_file_perms;
allow hal_sensors_default dmabuf_system_heap_device:chr_file r_file_perms;

# allow sensor hal to use lock for keeping system awake for wake up
# events delivery.
wakelock_use(hal_sensors_default);

# allow sensor hal to use ashmem fd from system_server.
allow hal_sensors_default system_server:fd use;
Group all HAL impls using haldomain attribute This marks all HAL domain implementations with the haldomain attribute so that rules can be written which apply to all HAL implementations. This follows the pattern used for appdomain, netdomain and bluetoothdomain. Test: No change to policy according to sesearch. Bug: 34180936 Change-Id: I0cfe599b0d49feed36538503c226dfce41eb65f6 2017-01-11 00:54:25 +01:00			`type hal_sensors_default, domain;`
Switch Sensors HAL policy to _client/_server This switches Sensors HAL policy to the design which enables us to conditionally remove unnecessary rules from domains which are clients of Sensors HAL. Domains which are clients of Sensors HAL, such as system_server, are granted rules targeting hal_sensors only when the Sensors HAL runs in passthrough mode (i.e., inside the client's process). When the HAL runs in binderized mode (i.e., in another process/domain, with clients talking to the HAL over HwBinder IPC), rules targeting hal_sensors are not granted to client domains. Domains which offer a binderized implementation of Sensors HAL, such as hal_sensors_default domain, are always granted rules targeting hal_sensors. P. S. This commit also removes allow system_server sensors_device:chr_file rw_file_perms because this is device-specific and thus not needed in device-agnostic policy. The device-specific policy of the affected devices already has this rule. Test: Device boots, no new denials Test: adb shell dumpsys sensorservice lists tons of sensors Test: Proprietary sensors test app indicates that there are sensors and that the app can register to listen for updates for sensors and that such updates arrive to the app. Bug: 34170079 Change-Id: I61bf779070eabcb64ae73724d62b6e837319a668 2017-03-13 23:13:52 +01:00			`hal_server_domain(hal_sensors_default, hal_sensors)`
Add sepolicy for sensors Adding sepoilcy for sensors. Test: Sensors work. Change-Id: Ibbf0c1a22654a17b1573e3761ea9ccd816150255 2016-11-29 21:26:51 +01:00
sepolicy: make exec_types in /vendor a subset of vendor_file_type We install all default hal implementations in /vendor/bin/hw along with a few domains that are defined in vendor policy and installed in /vendor. These files MUST be a subset of the global 'vendor_file_type' which is used to address all files installed in /vendor throughout the policy. Bug: 36463595 Test: Boot sailfish without any new denials Change-Id: I3d26778f9a26f9095f49d8ecc12f2ec9d2f4cb41 Signed-off-by: Sandeep Patil <sspatil@google.com> 2017-04-10 22:03:28 +02:00			`type hal_sensors_default_exec, exec_type, vendor_file_type, file_type;`
Add sepolicy for sensors Adding sepoilcy for sensors. Test: Sensors work. Change-Id: Ibbf0c1a22654a17b1573e3761ea9ccd816150255 2016-11-29 21:26:51 +01:00			`init_daemon_domain(hal_sensors_default)`
Restrict access to hwservicemanager This adds fine-grained policy about who can register and find which HwBinder services in hwservicemanager. Test: Play movie in Netflix and Google Play Movies Test: Play video in YouTube app and YouTube web page Test: In Google Camera app, take photo (HDR+ and conventional), record video (slow motion and normal), and check that photos look fine and videos play back with sound. Test: Cast screen to a Google Cast device Test: Get location fix in Google Maps Test: Make and receive a phone call, check that sound works both ways and that disconnecting the call frome either end works fine. Test: Run RsHelloCompute RenderScript demo app Test: Run fast subset of media CTS tests: make and install CtsMediaTestCases.apk adb shell am instrument -e size small \ -w 'android.media.cts/android.support.test.runner.AndroidJUnitRunner' Test: Play music using Google Play music Test: Adjust screen brightness via the slider in Quick Settings Test: adb bugreport Test: Enroll in fingerprint screen unlock, unlock screen using fingerprint Test: Apply OTA update: Make some visible change, e.g., rename Settings app. make otatools && \ make dist Ensure device has network connectivity ota_call.py -s <serial here> --file out/dist/sailfish-ota-*.zip Confirm the change is now live on the device Bug: 34454312 (cherry picked from commit 632bc494f199d9d85c37c1751667fe41f4b094cb) Merged-In: Iecf74000e6c68f01299667486f3c767912c076d3 Change-Id: I7a9a487beaf6f30c52ce08e04d415624da49dd31 2017-04-14 04:05:27 +02:00
			`allow hal_sensors_default fwk_scheduler_hwservice:hwservice_manager find;`
Allow sensor to use gralloc handle and access ion device Allow sensor hal to sue gralloc handle and access ion device so that sensor direct report feature can function correctly when HardwareBuffer shared memory is used. Test: SensorDirectReportTest passes without setenforce 0 Change-Id: I2068f6f4a8ac15da40126892e1326e0b90a6576f Merged-In: I2068f6f4a8ac15da40126892e1326e0b90a6576f 2017-04-28 00:23:08 +02:00
Add input_device permission to hal_sensors_default This is done so that /dev/input/event* nodes can be read by dynamic sensors framework. Bug: 38511270 Change-Id: Ib017c5621a8b7e08ddfa088453d061a6537a2a1c 2018-01-19 21:23:35 +01:00			`allow hal_sensors_default input_device:dir r_dir_perms;`
			`allow hal_sensors_default input_device:chr_file r_file_perms;`

Allow sensor hal to use wakelock Added permission related to use of wake lock. Wakelock in sensor HAL is used to gurantee delivery of wake up sensor events before system go back to sleep. Bug: 63995095 Test: QCOM and nanohub sensor hal are able to acquire wakelock successfuly. Change-Id: Id4ac3552e18a1cad252017e3dc9ab3d4be8d4ab9 2017-09-12 23:44:02 +02:00			`# Allow sensor hals to access and use gralloc memory allocated by`
			`# android.hardware.graphics.allocator`
Allow sensor to use gralloc handle and access ion device Allow sensor hal to sue gralloc handle and access ion device so that sensor direct report feature can function correctly when HardwareBuffer shared memory is used. Test: SensorDirectReportTest passes without setenforce 0 Change-Id: I2068f6f4a8ac15da40126892e1326e0b90a6576f Merged-In: I2068f6f4a8ac15da40126892e1326e0b90a6576f 2017-04-28 00:23:08 +02:00			`allow hal_sensors_default hal_graphics_allocator_default:fd use;`
			`allow hal_sensors_default ion_device:chr_file r_file_perms;`
Add missing permission for accessing the DMA-BUF system heap This patch fixes the following denials: avc: denied { open } for comm="composer@2.4-se" path="/dev/dma_heap/system" dev="tmpfs" ino=700 scontext=u:r:hal_graphics_composer_default:s0 tcontext=u:object_r:dmabuf_system_heap_device:s0 tclass=chr_file permissive=1 avc: denied { open } for comm="android.hardwar" path="/dev/dma_heap/system" dev="tmpfs" ino=700 scontext=u:r:hal_sensors_default:s0 tcontext=u:object_r:dmabuf_system_heap_device:s0 tclass=chr_file permissive=1 avc: denied { open } for comm="android.hardwar" path="/dev/dma_heap/system" dev="tmpfs" ino=700 scontext=u:r:hal_camera_default:s0 tcontext=u:object_r:dmabuf_system_heap_device:s0 tclass=chr_file permissive=1 avc: denied { open } for comm="BootAnimation" path="/dev/dma_heap/system" dev="tmpfs" ino=700 scontext=u:r:bootanim:s0 tcontext=u:object_r:dmabuf_system_heap_device:s0 tclass=chr_file permissive=1 avc: denied { open } for comm="Binder:470_2" path="/dev/dma_heap/system" dev="tmpfs" ino=700 scontext=u:r:surfaceflinger:s0 tcontext=u:object_r:dmabuf_system_heap_device:s0 tclass=chr_file permissive=1 avc: denied { read } for comm="HwBinder:946_2" name="system" dev="tmpfs" ino=588 scontext=u:r:cameraserver:s0 tcontext=u:object_r:dmabuf_system_heap_device:s0 tclass=chr_file permissive=1 avc: denied { open } for comm="HwBinder:946_2" path="/dev/dma_heap/system" dev="tmpfs" ino=588 scontext=u:r:cameraserver:s0 tcontext=u:object_r:dmabuf_system_heap_device:s0 tclass=chr_file permissive=1 Bug: 178865267 Test: boot without these denials Signed-off-by: Hyesoo Yu <hyesoo.yu@samsung.com> Change-Id: Ic31dffd1328a8693b721433e1dcbbc650d3a3c07 2021-02-16 06:57:42 +01:00			`allow hal_sensors_default dmabuf_system_heap_device:chr_file r_file_perms;`
Allow sensor hal to use wakelock Added permission related to use of wake lock. Wakelock in sensor HAL is used to gurantee delivery of wake up sensor events before system go back to sleep. Bug: 63995095 Test: QCOM and nanohub sensor hal are able to acquire wakelock successfuly. Change-Id: Id4ac3552e18a1cad252017e3dc9ab3d4be8d4ab9 2017-09-12 23:44:02 +02:00
			`# allow sensor hal to use lock for keeping system awake for wake up`
			`# events delivery.`
			`wakelock_use(hal_sensors_default);`
sepolicy: ashmem entry point for libcutils This duplicated ashmem device is intended to replace ashmemd. Ashmem fd has a label of the domain that opens it. Now with ashmemd removed, ashmem fds can have labels other than "ashmemd", e.g. "system_server". We add missing permissions to make ashmem fds usable. Bug: 139855428 Test: boot device Change-Id: Iec8352567f1e4f171f76db1272935eee59156954 2019-09-24 23:43:00 +02:00
			`# allow sensor hal to use ashmem fd from system_server.`
			`allow hal_sensors_default system_server:fd use;`