Files
device_google_wahoo/sepolicy
Max Bires b387500a64 Fixing the following denials in order to prep ims for enforcing
If there is no security issue with having ims write to ims_socket, then
I am fine with granting the permission in order to hurry up the
enforcing status of this domain.

denied { read } for pid=888 comm="imsdatadaemon" name="timestamp_switch"
dev="sysfs" ino=27246 scontext=u:r:ims:s0 tcontext=u:object_r:sysfs:s0
tclass=file

denied { open } for pid=888 comm="imsdatadaemon"
path="/sys/module/diagchar/parameters/timestamp_switch" dev="sysfs"
ino=27246 scontext=u:r:ims:s0 tcontext=u:object_r:sysfs:s0 tclass=file

denied { read } for pid=1326 comm="imsrcsd" name="timestamp_switch"
dev="sysfs" ino=27246 scontext=u:r:hal_rcsservice:s0
tcontext=u:object_r:sysfs:s0 tclass=file

denied { write } for pid=1077 comm="ims_rtp_daemon" name="ims_datad"
dev="tmpfs" ino=27069 scontext=u:r:ims:s0
tcontext=u:object_r:ims_socket:s0 tclass=sock_file

Bug: 34784662
Test: These denials no longer appear
Change-Id: I95d8b62d73fae35fca5e292e6927c4663db76e6f
2017-05-22 10:52:16 -07:00
..
2017-05-11 17:07:15 +00:00
2017-04-12 12:38:03 +00:00
2017-04-11 01:26:29 -07:00
2017-05-03 17:53:14 -07:00
2017-04-21 11:21:57 -07:00
2017-05-09 13:19:13 -07:00
2017-05-11 17:07:15 +00:00
2017-05-11 17:07:15 +00:00
2017-05-20 14:56:11 -07:00
2017-05-19 17:04:08 +00:00
2017-04-27 15:39:52 -07:00
2017-05-11 17:07:15 +00:00
2017-05-05 07:35:46 -07:00
2017-04-24 21:54:01 +00:00