Still M0 placeholder (starts, logs, idles) — no device-access code yet, so nothing to deny. Also fixes rpi5's copy missing coredomain, which its own sibling file's comment (rpi4) says is required since the exec type is system_file_type.
25 lines
1.4 KiB
Plaintext
25 lines
1.4 KiB
Plaintext
# pawlet.androidauto-daemon — native Android Auto head-unit protocol engine
|
|
# (GPLv3, packages/apps/PawletAndroidAuto/native). Scoped domain rather than a
|
|
# stock system daemon type, since it will need raw USB host device access
|
|
# (AOAP/libusb) once the real protocol lands — mirrors the domain-isolation
|
|
# approach of hal_boot_control_pawlet_rpi.te, even though this isn't a real
|
|
# Treble HAL (no VINTF fragment, plain /system/bin daemon).
|
|
#
|
|
# M0: placeholder binary only (starts, logs, idles) — no device access rules
|
|
# yet, so nothing to deny; enforcing from the start. USB/AAudio/MediaCodec
|
|
# grants land alongside the milestones that need them (see PLAN.md in the
|
|
# app repo) — re-add `permissive pawlet_androidauto_daemon;` if a later
|
|
# milestone needs a permissive window to validate new denials before they're
|
|
# reconciled into allow rules here.
|
|
|
|
# coredomain: pawlet_androidauto_daemon_exec is system_file_type (installs to
|
|
# /system/bin), so the domain must be coredomain too — otherwise it's treated
|
|
# as a vendor domain executing/entering a system file, which trips Treble's
|
|
# vendor-vs-system neverallow rules (system/sepolicy/private/domain.te,
|
|
# "Do not allow vendor components to execute files from system"/"access
|
|
# entrypoint"/"access /system files" blocks).
|
|
type pawlet_androidauto_daemon, domain, coredomain;
|
|
type pawlet_androidauto_daemon_exec, exec_type, file_type, system_file_type;
|
|
|
|
init_daemon_domain(pawlet_androidauto_daemon)
|