a1c94c8d25
Disallowing other HALs access to video_device does not appear to be
enforceable.
(cherry picked from commit c26dd18aeb)
Bug: 37669506
Test: build policy. Neverallow rules are build time test and do not
impact the policy binary.
Change-Id: Iea401de08a63f3261a461f67b85113a9d838e88a
36 lines
1.4 KiB
Text
36 lines
1.4 KiB
Text
# HwBinder IPC from clients to server and callbacks
|
|
binder_call(hal_camera_client, hal_camera_server)
|
|
binder_call(hal_camera_server, hal_camera_client)
|
|
|
|
add_hwservice(hal_camera_server, hal_camera_hwservice)
|
|
allow hal_camera_client hal_camera_hwservice:hwservice_manager find;
|
|
|
|
# access /data/misc/camera
|
|
allow hal_camera camera_data_file:dir create_dir_perms;
|
|
allow hal_camera camera_data_file:file create_file_perms;
|
|
|
|
allow hal_camera video_device:dir r_dir_perms;
|
|
allow hal_camera video_device:chr_file rw_file_perms;
|
|
allow hal_camera camera_device:chr_file rw_file_perms;
|
|
allow hal_camera ion_device:chr_file rw_file_perms;
|
|
# Both the client and the server need to use the graphics allocator
|
|
allow { hal_camera_client hal_camera_server } hal_graphics_allocator:fd use;
|
|
|
|
# Allow hal_camera to use fd from app,gralloc,and ashmem HAL
|
|
allow hal_camera { appdomain -isolated_app }:fd use;
|
|
allow hal_camera surfaceflinger:fd use;
|
|
allow hal_camera hal_allocator_server:fd use;
|
|
|
|
###
|
|
### neverallow rules
|
|
###
|
|
|
|
# hal_camera should never execute any executable without a
|
|
# domain transition
|
|
neverallow hal_camera { file_type fs_type }:file execute_no_trans;
|
|
|
|
# hal_camera should never need network access. Disallow network sockets.
|
|
neverallow hal_camera domain:{ tcp_socket udp_socket rawip_socket } *;
|
|
|
|
# Only camera HAL may directly access the camera hardware
|
|
neverallow { halserverdomain -hal_camera_server } camera_device:chr_file *;
|