f1b92488f5
run-as won't communicate with shell via pipes. Allow it.
nnk@nnk:~$ adb shell "cat /dev/zero | run-as com.google.foo sh -c 'cat'"
/system/bin/sh: cat: <stdout>: Broken pipe
<4>[ 1485.483517] type=1400 audit(1402623577.085:25): avc: denied { read } for pid=6026 comm="run-as" path="pipe:[29823]" dev="pipefs" ino=29823 scontext=u:r:runas:s0 tcontext=u:r:shell:s0 tclass=fifo_file
read is definitely needed. Not sure about write, but adding it just
in case.
(cherry picked from commit 6c9c58884a)
Change-Id: Ifed6314588723063531982b45a56b902dfe32ea9
25 lines
876 B
Text
25 lines
876 B
Text
type runas, domain, mlstrustedsubject;
|
|
type runas_exec, exec_type, file_type;
|
|
|
|
# ndk-gdb invokes adb shell run-as.
|
|
domain_auto_trans(shell, runas_exec, runas)
|
|
allow runas adbd:process sigchld;
|
|
allow runas shell:fd use;
|
|
allow runas shell:fifo_file { read write };
|
|
allow runas devpts:chr_file { read write ioctl };
|
|
|
|
# run-as reads package information.
|
|
allow runas system_data_file:file r_file_perms;
|
|
|
|
# run-as checks and changes to the app data dir.
|
|
dontaudit runas self:capability dac_override;
|
|
allow runas app_data_file:dir { getattr search };
|
|
|
|
# run-as switches to the app UID/GID.
|
|
allow runas self:capability { setuid setgid };
|
|
|
|
# run-as switches to the app security context.
|
|
# read /seapp_contexts and /data/security/seapp_contexts
|
|
security_access_policy(runas)
|
|
selinux_check_context(runas) # validate context
|
|
allow runas non_system_app_set:process dyntransition; # setcon
|