2018-09-20 21:07:44 +02:00
|
|
|
type mediaswcodec, domain;
|
|
|
|
|
type mediaswcodec_exec, system_file_type, exec_type, file_type;
|
|
|
|
|
|
2019-04-30 14:09:28 +02:00
|
|
|
hal_server_domain(mediaswcodec, hal_codec2)
|
|
|
|
|
|
|
|
|
|
# mediaswcodec may use an input surface from a different Codec2 service or an
|
|
|
|
|
# OMX service
|
|
|
|
|
hal_client_domain(mediaswcodec, hal_codec2)
|
|
|
|
|
hal_client_domain(mediaswcodec, hal_omx)
|
2018-09-20 21:07:44 +02:00
|
|
|
|
|
|
|
|
hal_client_domain(mediaswcodec, hal_allocator)
|
|
|
|
|
hal_client_domain(mediaswcodec, hal_graphics_allocator)
|
|
|
|
|
|
2019-04-30 14:09:28 +02:00
|
|
|
crash_dump_fallback(mediaswcodec)
|
|
|
|
|
|
|
|
|
|
# mediaswcodec_server should never execute any executable without a
|
|
|
|
|
# domain transition
|
|
|
|
|
neverallow mediaswcodec { file_type fs_type }:file execute_no_trans;
|
|
|
|
|
|
|
|
|
|
# Media processing code is inherently risky and thus should have limited
|
|
|
|
|
# permissions and be isolated from the rest of the system and network.
|
|
|
|
|
# Lengthier explanation here:
|
|
|
|
|
# https://android-developers.googleblog.com/2016/05/hardening-media-stack.html
|
|
|
|
|
neverallow mediaswcodec domain:{ tcp_socket udp_socket rawip_socket } *;
|
|
|
|
|
|
2020-09-11 23:00:59 +02:00
|
|
|
allow mediaswcodec dmabuf_system_heap_device:chr_file r_file_perms;
|
2021-01-12 21:05:20 +01:00
|
|
|
allow mediaswcodec dmabuf_system_secure_heap_device:chr_file r_file_perms;
|
