1# applies all permissions to hal_omx NOT hal_omx_server 2# since OMX must always be in its own process. 3 4binder_call(hal_omx_server, binderservicedomain) 5binder_call(hal_omx_server, { appdomain -isolated_app }) 6 7# Allow hal_omx_server access to composer sync fences 8allow hal_omx_server hal_graphics_composer:fd use; 9 10allow hal_omx_server ion_device:chr_file rw_file_perms; 11allow hal_omx_server hal_camera:fd use; 12 13crash_dump_fallback(hal_omx_server) 14 15# Recieve gralloc buffer FDs from bufferhubd. Note that hal_omx_server never 16# directly connects to bufferhubd via PDX. Instead, a VR app acts as a bridge 17# between those two: it talks to hal_omx_server via Binder and talks to bufferhubd 18# via PDX. Thus, there is no need to use pdx_client macro. 19allow hal_omx_server bufferhubd:fd use; 20 21hal_attribute_hwservice(hal_omx, hal_omx_hwservice) 22 23allow hal_omx_client hidl_token_hwservice:hwservice_manager find; 24 25binder_call(hal_omx_client, hal_omx_server) 26binder_call(hal_omx_server, hal_omx_client) 27 28### 29### neverallow rules 30### 31 32# hal_omx_server should never execute any executable without a 33# domain transition 34neverallow hal_omx_server { file_type fs_type }:file execute_no_trans; 35 36# The goal of the mediaserver split is to place media processing code into 37# restrictive sandboxes with limited responsibilities and thus limited 38# permissions. Example: Audioserver is only responsible for controlling audio 39# hardware and processing audio content. Cameraserver does the same for camera 40# hardware/content. Etc. 41# 42# Media processing code is inherently risky and thus should have limited 43# permissions and be isolated from the rest of the system and network. 44# Lengthier explanation here: 45# https://android-developers.googleblog.com/2016/05/hardening-media-stack.html 46neverallow hal_omx_server domain:{ tcp_socket udp_socket rawip_socket } *; 47