9ec532752d
Any FUSE filesystem will receive the 'fuse' type when mounted. It is possible to change this behaviour by specifying the "context=" or "fscontext=" option in mount(). Because 'fuse' has historically been used only for the emulated storage, it also received the 'sdcard_type' attribute. Replace the 'sdcard_type' attribute from 'fuse' with the new 'fusefs_type'. This attribute can be attached on derived types (such as app_fusefs). This change: - Remove the neverallow restriction on this new type. This means any custom FUSE implementation can be mounted/unmounted (if the correct allow rule is added). See domain.te. - Change the attribute of 'fuse' from 'sdcard_type' to 'fusefs_type'. See file.te. - Modify all references to 'sdcard_type' to explicitly include 'fuse' for compatibility reason. Bug: 177481425 Bug: 190804537 Test: Build and boot aosp_cf_x86_64_phone-userdebug Change-Id: Id4e410a049f72647accd4c3cf43eaa55e94c318f
73 lines
2.8 KiB
Text
73 lines
2.8 KiB
Text
# mediaextractor - multimedia daemon
|
|
type mediaextractor, domain;
|
|
type mediaextractor_exec, system_file_type, exec_type, file_type;
|
|
type mediaextractor_tmpfs, file_type;
|
|
|
|
typeattribute mediaextractor mlstrustedsubject;
|
|
|
|
binder_use(mediaextractor)
|
|
binder_call(mediaextractor, binderservicedomain)
|
|
binder_call(mediaextractor, appdomain)
|
|
binder_service(mediaextractor)
|
|
|
|
add_service(mediaextractor, mediaextractor_service)
|
|
allow mediaextractor mediametrics_service:service_manager find;
|
|
allow mediaextractor hidl_token_hwservice:hwservice_manager find;
|
|
|
|
allow mediaextractor system_server:fd use;
|
|
|
|
hal_client_domain(mediaextractor, hal_cas)
|
|
hal_client_domain(mediaextractor, hal_allocator)
|
|
|
|
r_dir_file(mediaextractor, cgroup)
|
|
r_dir_file(mediaextractor, cgroup_v2)
|
|
allow mediaextractor proc_meminfo:file r_file_perms;
|
|
|
|
crash_dump_fallback(mediaextractor)
|
|
|
|
# allow mediaextractor read permissions for file sources
|
|
allow mediaextractor { sdcard_type fuse }:file { getattr read };
|
|
allow mediaextractor media_rw_data_file:file { getattr read };
|
|
allow mediaextractor { app_data_file privapp_data_file }:file { getattr read };
|
|
|
|
# Read resources from open apk files passed over Binder
|
|
allow mediaextractor apk_data_file:file { read getattr };
|
|
allow mediaextractor asec_apk_file:file { read getattr };
|
|
allow mediaextractor ringtone_file:file { read getattr };
|
|
|
|
# overlay package access
|
|
allow mediaextractor vendor_overlay_file:file { read map };
|
|
|
|
# scan extractor library directory to dynamically load extractors
|
|
allow mediaextractor system_file:dir { read open };
|
|
|
|
###
|
|
### neverallow rules
|
|
###
|
|
|
|
# mediaextractor should never execute any executable without a
|
|
# domain transition
|
|
neverallow mediaextractor { file_type fs_type }:file execute_no_trans;
|
|
|
|
# The goal of the mediaserver split is to place media processing code into
|
|
# restrictive sandboxes with limited responsibilities and thus limited
|
|
# permissions. Example: Audioserver is only responsible for controlling audio
|
|
# hardware and processing audio content. Cameraserver does the same for camera
|
|
# hardware/content. Etc.
|
|
#
|
|
# 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 mediaextractor domain:{ udp_socket rawip_socket } *;
|
|
neverallow mediaextractor { domain userdebug_or_eng(`-su') }:tcp_socket *;
|
|
|
|
# mediaextractor should not be opening /data files directly. Any files
|
|
# it touches (with a few exceptions) need to be passed to it via a file
|
|
# descriptor opened outside the process.
|
|
neverallow mediaextractor {
|
|
data_file_type
|
|
-zoneinfo_data_file # time zone data from /data/misc/zoneinfo
|
|
userdebug_or_eng(`-apk_data_file') # for loading media extractor plugins
|
|
with_native_coverage(`-method_trace_data_file')
|
|
}:file open;
|