platform_system_sepolicy/private/runas_app.te

19 lines
717 B
Text
Raw Normal View History

typeattribute runas_app coredomain;
app_domain(runas_app)
untrusted_app_domain(runas_app)
net_domain(runas_app)
bluetooth_domain(runas_app)
# The ability to call exec() on files in the apps home directories
# when using run-as on a debuggable app. Used to run lldb/ndk-gdb/simpleperf,
# which are copied to the apps home directories.
allow runas_app app_data_file:file execute_no_trans;
# Allow lldb/ndk-gdb/simpleperf to read maps of debuggable app processes.
r_dir_file(runas_app, untrusted_app_all)
# Allow lldb/ndk-gdb/simpleperf to ptrace attach to debuggable app processes.
Allow permissions needed for gdb debugging system/sepolicy commit ffa2b61330c93bac780cde9eb5bc72ae60cd910b introduced the runas_app SELinux domain, which changed how we perform debugging of Android applications. This broke Android Studio's lldb. From bugreport: Debugging an app containing native code using ndk-gdb or Android Studio's lldb currently fails. There is an selinux error in logcat about a sigchld denial. Studio can still debug Java-only apps. In Android Studio, starting the debugger on an app with native code produces this selinux denial: 01-30 06:58:02.089 13449 13449 W lldb-server: type=1400 audit(0.0:831): avc: denied { sigchld } for scontext=u:r:untrusted_app_27:s0:c167,c256,c512,c768 tcontext=u:r:runas_app:s0:c167,c256,c512,c768 tclass=process permissive=0 app=com.android.ndktestapp With "set enforce 0", I also see a sigstop denial: 01-30 07:31:12.209 15672 15672 I lldb-server: type=1400 audit(0.0:1290): avc: denied { sigstop } for scontext=u:r:runas_app:s0:c167,c256,c512,c768 tcontext=u:r:untrusted_app_27:s0:c167,c256,c512,c768 tclass=process permissive=1 app=com.android.ndktestapp In gdb-server.log, Studio reports this error while trying to start lldb-server: 1548831482.091491938 GDBRemoteCommunicationServerLLGS::Handle_vAttach attempting to attach to pid 13379 1548831482.091519117 GDBRemoteCommunicationServerLLGS::AttachToProcess pid 13379 1548831482.092242956 GDBRemoteCommunicationServerLLGS::Handle_vAttach failed to attach to pid 13379: Permission denied Using ndk-gdb (e.g. on the NdkGdbSample) produces the same sort of selinux denial: 01-30 07:11:26.742 13926 13926 W arm64-gdbserver: type=1400 audit(0.0:833): avc: denied { sigchld } for scontext=u:r:untrusted_app_27:s0:c166,c256,c512,c768 tcontext=u:r:runas_app:s0:c166,c256,c512,c768 tclass=process permissive=0 app=com.android.developer.ndkgdbsample If I use "setenforce 0", I see more denials logged (signal and sigstop): 01-30 07:30:23.346 15478 15478 I arm64-gdbserver: type=1400 audit(0.0:1287): avc: denied { signal } for scontext=u:r:runas_app:s0:c166,c256,c512,c768 tcontext=u:r:untrusted_app_27:s0:c166,c256,c512,c768 tclass=process permissive=1 app=com.android.developer.ndkgdbsample 01-30 07:30:23.349 15478 15478 I arm64-gdbserver: type=1400 audit(0.0:1288): avc: denied { sigstop } for scontext=u:r:runas_app:s0:c166,c256,c512,c768 tcontext=u:r:untrusted_app_27:s0:c166,c256,c512,c768 tclass=process permissive=1 app=com.android.developer.ndkgdbsample ndk-gdb times out and prints an error: rprichard@cashew:/x/ndk/ndk/samples/NdkGdbSample$ /x/android-ndk-r19/ndk-gdb --launch Redirecting gdbserver output to /tmp/gdbclient.log ... Error: unable to connect to device. Remote communication error. Target disconnected.: Connection reset by peer. gdbclient.log shows that gdbserver hasn't started listening to its Unix socket yet: rprichard@cashew:/x/ndk/ndk/samples/NdkGdbSample$ cat /tmp/gdbclient.log Attached; pid = 14232 Normal output looks like this: rprichard@cashew:/x/ndk/ndk/samples/NdkGdbSample$ cat /tmp/gdbclient.log Attached; pid = 27799 Listening on Unix domain socket '/data/data/com.android.developer.ndkgdbsample/debug_socket' Remote debugging from host 127.0.0.0 Test: compiles and builds Bug: 123612207 Change-Id: Ia9a711cc54cc044c0817a7c17eb4506015adb393
2019-01-30 22:19:36 +01:00
allow runas_app untrusted_app_all:process { ptrace signal sigstop };
allow runas_app untrusted_app_all:unix_stream_socket connectto system/sepolicy commit ffa2b61330c93bac780cde9eb5bc72ae60cd910b introduced the runas_app SELinux domain, which changed how we perform debugging and profiling of Android applications. This broke Android Studio's profiling tool. Android Studio's profiling tool has the run-as spawned application connect to an app created unix domain sockets in the abstract namespace. Note: this differs from system/sepolicy commit 3e5668f173374a98ff13b94523960c5bf14c8b72, which allows connections in the reverse direction (from app to runas_app). That change (b/123297648) was made for a different part of Android Studio, Android Studio Instant Run. Addresses the following denial: 2019-02-08 00:59:14.563 15560-15560/? W/connector: type=1400 audit(0.0:645): avc: denied { connectto } for path=00436C69656E74 scontext=u:r:runas_app:s0:c188,c256,c512,c768 tcontext=u:r:untrusted_app_27:s0:c188,c256,c512,c768 tclass=unix_stream_socket permissive=0 app=com.example.hellojni (hex decode of 00436C69656E74 is "Client") 2019-01-31 17:25:16.060 19975-19975/? W/transport: type=1400 audit(0.0:8146): avc: denied { connectto } for path=00416E64726F696453747564696F5472616E73706F72744167656E743139383839 scontext=u:r:runas_app:s0:c512,c768 tcontext=u:r:untrusted_app_25:s0:c512,c768 tclass=unix_stream_socket permissive=0 app=com.example.android.displayingbitmaps (hex decode of 00416E64726F696453747564696F5472616E73706F72744167656E743139383839 is "AndroidStudioTransportAgent19889") Bug: 120445954 Test: manual Change-Id: I9ca1c338dcbc75cb3fbd7bf93a348f9276363dc1
2019-02-08 20:30:13 +01:00
allow runas_app untrusted_app_all:unix_stream_socket connectto;