2012-01-04 18:33:27 +01:00
|
|
|
# ueventd seclabel is specified in init.rc since
|
|
|
|
# it lives in the rootfs and has no unique file type.
|
2017-05-15 22:19:03 +02:00
|
|
|
type ueventd, domain;
|
2019-01-24 00:07:40 +01:00
|
|
|
type ueventd_tmpfs, file_type;
|
Allow /dev/klog access, drop mknod and __null__ access
Allow vold, healthd, slideshow, and watchdogd access to /dev/kmsg.
These processes log to the kernel dmesg ring buffer, so they need
write access to that file.
Addresses the following denials:
avc: denied { write } for pid=134 comm="watchdogd" name="kmsg" dev="tmpfs" ino=9248 scontext=u:r:watchdogd:s0 tcontext=u:object_r:kmsg_device:s0 tclass=chr_file permissive=0
avc: denied { write } for pid=166 comm="healthd" name="kmsg" dev="tmpfs" ino=9248 scontext=u:r:healthd:s0 tcontext=u:object_r:kmsg_device:s0 tclass=chr_file permissive=0
avc: denied { write } for pid=180 comm="vold" name="kmsg" dev="tmpfs" ino=9248 scontext=u:r:vold:s0 tcontext=u:object_r:kmsg_device:s0 tclass=chr_file permissive=0
These denials were triggered by the change in
https://android-review.googlesource.com/151209 . Prior to that change,
any code which called klog_init would (unnecessarily) create the
device node themselves, rather than using the already existing device
node.
Drop special /dev/__null__ handling from watchdogd. As of
https://android-review.googlesource.com/148288 , watchdogd no longer
creates it's own /dev/null device, so it's unnecessary for us
to allow for it.
Drop mknod from healthd, slideshow, and watchdogd. healthd and slideshow
only needed mknod to create /dev/__kmsg__, which is now obsolete.
watchdogd only needed mknod to create /dev/__kmsg__ and /dev/__null__,
which again is now obsolete.
Bug: 21242418
Change-Id: If01c8001084575e7441253f0fa8b4179ae33f534
2015-06-06 16:42:37 +02:00
|
|
|
|
2016-07-26 18:46:20 +02:00
|
|
|
# Write to /dev/kmsg.
|
|
|
|
allow ueventd kmsg_device:chr_file rw_file_perms;
|
Allow /dev/klog access, drop mknod and __null__ access
Allow vold, healthd, slideshow, and watchdogd access to /dev/kmsg.
These processes log to the kernel dmesg ring buffer, so they need
write access to that file.
Addresses the following denials:
avc: denied { write } for pid=134 comm="watchdogd" name="kmsg" dev="tmpfs" ino=9248 scontext=u:r:watchdogd:s0 tcontext=u:object_r:kmsg_device:s0 tclass=chr_file permissive=0
avc: denied { write } for pid=166 comm="healthd" name="kmsg" dev="tmpfs" ino=9248 scontext=u:r:healthd:s0 tcontext=u:object_r:kmsg_device:s0 tclass=chr_file permissive=0
avc: denied { write } for pid=180 comm="vold" name="kmsg" dev="tmpfs" ino=9248 scontext=u:r:vold:s0 tcontext=u:object_r:kmsg_device:s0 tclass=chr_file permissive=0
These denials were triggered by the change in
https://android-review.googlesource.com/151209 . Prior to that change,
any code which called klog_init would (unnecessarily) create the
device node themselves, rather than using the already existing device
node.
Drop special /dev/__null__ handling from watchdogd. As of
https://android-review.googlesource.com/148288 , watchdogd no longer
creates it's own /dev/null device, so it's unnecessary for us
to allow for it.
Drop mknod from healthd, slideshow, and watchdogd. healthd and slideshow
only needed mknod to create /dev/__kmsg__, which is now obsolete.
watchdogd only needed mknod to create /dev/__kmsg__ and /dev/__null__,
which again is now obsolete.
Bug: 21242418
Change-Id: If01c8001084575e7441253f0fa8b4179ae33f534
2015-06-06 16:42:37 +02:00
|
|
|
|
2018-09-07 00:19:40 +02:00
|
|
|
allow ueventd self:global_capability_class_set { chown mknod net_admin setgid fsetid sys_rawio dac_override dac_read_search fowner };
|
2013-10-06 21:36:11 +02:00
|
|
|
allow ueventd device:file create_file_perms;
|
2017-01-09 23:57:03 +01:00
|
|
|
|
2016-09-10 01:27:17 +02:00
|
|
|
r_dir_file(ueventd, rootfs)
|
2017-09-26 21:58:29 +02:00
|
|
|
|
|
|
|
# ueventd needs write access to files in /sys to regenerate uevents
|
|
|
|
allow ueventd sysfs_type:file w_file_perms;
|
|
|
|
r_dir_file(ueventd, sysfs_type)
|
|
|
|
allow ueventd sysfs_type:{ file lnk_file } { relabelfrom relabelto setattr };
|
|
|
|
allow ueventd sysfs_type:dir { relabelfrom relabelto setattr };
|
2013-10-06 21:36:11 +02:00
|
|
|
allow ueventd tmpfs:chr_file rw_file_perms;
|
|
|
|
allow ueventd dev_type:dir create_dir_perms;
|
|
|
|
allow ueventd dev_type:lnk_file { create unlink };
|
2016-06-03 00:06:02 +02:00
|
|
|
allow ueventd dev_type:chr_file { getattr create setattr unlink };
|
|
|
|
allow ueventd dev_type:blk_file { getattr relabelfrom relabelto create setattr unlink };
|
2016-05-17 06:12:17 +02:00
|
|
|
allow ueventd self:netlink_kobject_uevent_socket create_socket_perms_no_ioctl;
|
2013-10-06 21:36:11 +02:00
|
|
|
allow ueventd efs_file:dir search;
|
|
|
|
allow ueventd efs_file:file r_file_perms;
|
2014-05-23 17:26:19 +02:00
|
|
|
|
2016-09-10 01:27:17 +02:00
|
|
|
# Get SELinux enforcing status.
|
|
|
|
r_dir_file(ueventd, selinuxfs)
|
|
|
|
|
2017-04-02 02:17:12 +02:00
|
|
|
# Access for /vendor/ueventd.rc and /vendor/firmware
|
2017-09-26 21:58:29 +02:00
|
|
|
r_dir_file(ueventd, { vendor_file_type -vendor_app_file -vendor_overlay_file })
|
2017-04-02 02:17:12 +02:00
|
|
|
|
2017-03-24 23:02:13 +01:00
|
|
|
# Get file contexts for new device nodes
|
|
|
|
allow ueventd file_contexts_file:file r_file_perms;
|
|
|
|
|
2014-05-23 17:26:19 +02:00
|
|
|
# Use setfscreatecon() to label /dev directories and files.
|
|
|
|
allow ueventd self:process setfscreate;
|
2015-03-03 05:10:48 +01:00
|
|
|
|
2018-05-17 12:28:33 +02:00
|
|
|
# Allow ueventd to read androidboot.android_dt_dir from kernel cmdline.
|
|
|
|
allow ueventd proc_cmdline:file r_file_perms;
|
|
|
|
|
2018-06-01 12:28:59 +02:00
|
|
|
# Everything is labeled as rootfs in recovery mode. ueventd has to execute
|
|
|
|
# the dynamic linker and shared libraries.
|
|
|
|
recovery_only(`
|
|
|
|
allow ueventd rootfs:file { r_file_perms execute };
|
|
|
|
')
|
|
|
|
|
2018-06-19 03:34:15 +02:00
|
|
|
# Suppress denials for ueventd to getattr /postinstall. This occurs when the
|
|
|
|
# linker tries to resolve paths in ld.config.txt.
|
|
|
|
dontaudit ueventd postinstall_mnt_dir:dir getattr;
|
|
|
|
|
2018-08-01 00:00:20 +02:00
|
|
|
# ueventd loads modules in response to modalias events.
|
|
|
|
allow ueventd self:global_capability_class_set sys_module;
|
|
|
|
allow ueventd vendor_file:system module_load;
|
|
|
|
allow ueventd kernel:key search;
|
|
|
|
|
2015-03-03 05:10:48 +01:00
|
|
|
#####
|
|
|
|
##### neverallow rules
|
|
|
|
#####
|
|
|
|
|
|
|
|
# ueventd must never set properties, otherwise deadlocks may occur.
|
|
|
|
# https://android-review.googlesource.com/#/c/133120/6/init/devices.cpp@941
|
|
|
|
# No writing to the property socket, connecting to init, or setting properties.
|
|
|
|
neverallow ueventd property_socket:sock_file write;
|
|
|
|
neverallow ueventd init:unix_stream_socket connectto;
|
|
|
|
neverallow ueventd property_type:property_service set;
|
2016-06-03 00:06:02 +02:00
|
|
|
|
|
|
|
# Restrict ueventd access on block devices to maintenence operations.
|
|
|
|
neverallow ueventd dev_type:blk_file ~{ getattr relabelfrom relabelto create setattr unlink };
|
|
|
|
|
2018-11-14 02:55:06 +01:00
|
|
|
# Only relabelto as we would never want to relabelfrom port_device
|
|
|
|
neverallow ueventd port_device:chr_file ~{ getattr create setattr unlink relabelto };
|
2018-09-13 20:07:14 +02:00
|
|
|
|
|
|
|
# Nobody should be able to ptrace ueventd
|
|
|
|
neverallow * ueventd:process ptrace;
|