WAI
Status Update
Comments
am...@google.com <am...@google.com> #2
Please provide sample project or apk to reproduce the issue. Also mention the steps to be followed for reproducing the issue with the given sample project or apk.
ta...@gmail.com <ta...@gmail.com> #5
I am seeing the same issue with the ADM using API 24.
za...@gmail.com <za...@gmail.com> #6
The same for me too =(
al...@gmail.com <al...@gmail.com> #7
I m also facing same problem. Does anybody has a solution
al...@gmail.com <al...@gmail.com> #8
Sorry for the inconvenience -- we are currently working on a fix. This thread will be updated when the patch is released.
Description
QPP1.190205.018.B3
* Is this a regression from P to Q?
Yes, worked on P, doesn't work on Q, change is undocumented.
* What device are you using? (for example, Pixel XL)
Emulator
* What are the steps to reproduce the problem? (Please provide the minimal reproducible test case.)
Try to run a binary from the apps private data dir (e.g. /data/data/<pkg/files).
* Issue Category e.g. Framework (platform), NDK (platform), Hardware (CPU, GPU, Sensor, Camera), ART (platform), Runtime Permissions etc
Framework (platform) / SELinux, Policy
* What was the expected result?
That I can run the binary.
* What was the actual result?
sh: <stdin>[31]: ./data/user/0/<pkg>/files/toybox: Permission denied
* Relevant logcat output.
W/sh: type=1400 audit(0.0:6585): avc: denied { execute_no_trans } for path="/data/data/eu.thedarken.sdm/files/toybox_sdm" dev="vdc" ino=115932 scontext=u:r:untrusted_app:s0:c110,c256,c512,c768 tcontext=u:object_r:app_data_file:s0:c110,c256,c512,c768 tclass=file permissive=0
* Link to captured Android bug report (shared privately in Drive.)
Previous APIs seem to have this explicitly enabled, but it's missing for API29?
Being allowed to execute your own binaries, e.g. a toybox is necessary for a lot of apps.