9b2e0cbeea
In kernel 4.7, the capability and capability2 classes were split apart
from cap_userns and cap2_userns (see kernel commit
8e4ff6f228e4722cac74db716e308d1da33d744f). Since then, Android cannot be
run in a container with SELinux in enforcing mode.
This change applies the existing capability rules to user namespaces as
well as the root namespace so that Android running in a container
behaves the same on pre- and post-4.7 kernels.
This is essentially:
1. New global_capability_class_set and global_capability2_class_set
that match capability+cap_userns and capability2+cap2_userns,
respectively.
2. s/self:capability/self:global_capability_class_set/g
3. s/self:capability2/self:global_capability2_class_set/g
4. Add cap_userns and cap2_userns to the existing capability_class_set
so that it covers all capabilities. This set was used by several
neverallow and dontaudit rules, and I confirmed that the new
classes are still appropriate.
Test: diff new policy against old and confirm that all new rules add
only cap_userns or cap2_userns;
Boot ARC++ on a device with the 4.12 kernel.
Bug: crbug.com/754831
Change-Id: I4007eb3a2ecd01b062c4c78d9afee71c530df95f
73 lines
2.3 KiB
Text
73 lines
2.3 KiB
Text
# android user-space log manager
|
|
type logd, domain, mlstrustedsubject;
|
|
type logd_exec, exec_type, file_type;
|
|
|
|
# Read access to pseudo filesystems.
|
|
r_dir_file(logd, cgroup)
|
|
r_dir_file(logd, proc_kmsg)
|
|
r_dir_file(logd, proc_meminfo)
|
|
r_dir_file(logd, proc_net)
|
|
|
|
allow logd self:global_capability_class_set { setuid setgid setpcap sys_nice audit_control };
|
|
allow logd self:global_capability2_class_set syslog;
|
|
allow logd self:netlink_audit_socket { create_socket_perms_no_ioctl nlmsg_write };
|
|
allow logd kernel:system syslog_read;
|
|
allow logd kmsg_device:chr_file w_file_perms;
|
|
allow logd system_data_file:{ file lnk_file } r_file_perms;
|
|
allow logd pstorefs:dir search;
|
|
allow logd pstorefs:file r_file_perms;
|
|
userdebug_or_eng(`
|
|
# Access to /data/misc/logd/event-log-tags
|
|
allow logd misc_logd_file:dir r_dir_perms;
|
|
allow logd misc_logd_file:file rw_file_perms;
|
|
')
|
|
allow logd runtime_event_log_tags_file:file rw_file_perms;
|
|
|
|
# Access device logging gating property
|
|
get_prop(logd, device_logging_prop)
|
|
|
|
r_dir_file(logd, domain)
|
|
|
|
allow logd kernel:system syslog_mod;
|
|
|
|
control_logd(logd)
|
|
read_runtime_log_tags(logd)
|
|
|
|
allow runtime_event_log_tags_file tmpfs:filesystem associate;
|
|
# Typically harmlessly blindly trying to access via liblog
|
|
# event tag mapping while in the untrusted_app domain.
|
|
# Access for that domain is controlled and gated via the
|
|
# event log tag service (albeit at a performance penalty,
|
|
# expected to be locally cached).
|
|
dontaudit domain runtime_event_log_tags_file:file { open read };
|
|
|
|
###
|
|
### Neverallow rules
|
|
###
|
|
### logd should NEVER do any of this
|
|
|
|
# Block device access.
|
|
neverallow logd dev_type:blk_file { read write };
|
|
|
|
# ptrace any other app
|
|
neverallow logd domain:process ptrace;
|
|
|
|
# ... and nobody may ptrace me (except on userdebug or eng builds)
|
|
neverallow { domain userdebug_or_eng(`-crash_dump') } logd:process ptrace;
|
|
|
|
# Write to /system.
|
|
neverallow logd system_file:dir_file_class_set write;
|
|
|
|
# Write to files in /data/data or system files on /data
|
|
neverallow logd { app_data_file system_data_file }:dir_file_class_set write;
|
|
|
|
# Only init is allowed to enter the logd domain via exec()
|
|
neverallow { domain -init } logd:process transition;
|
|
neverallow * logd:process dyntransition;
|
|
|
|
# protect the event-log-tags file
|
|
neverallow {
|
|
domain
|
|
-init
|
|
-logd
|
|
} runtime_event_log_tags_file:file no_w_file_perms;
|