Thanks for the head up. I agree with all the points in the discussion. However, our use case is different. We use Boolean to tighten, not loosen, the run time environment.
Tai On 3/10/14, 3:01 PM, "Stephen Smalley" <[email protected]> wrote: >On 03/10/2014 02:55 PM, Tai Nguyen (tainguye) wrote: >> This issue is actually related to boolean. The result is different >>because >> our booleans are not set consistently in these modes. >> Thus, we actually have different policy. In the emulator mode, shell is >> allow to execute shell_data_file. >> So, avoiding boolean may make troubleshooting a little bit easier. > >Ok. cts in AOSP master now forbids booleans in policy, and we have >recently dropped them from our trees: >https://android-review.googlesource.com/#/c/80456/ > >Other pending cts tests related to SELinux in AOSP master: >https://android-review.googlesource.com/#/c/82861/ >https://android-review.googlesource.com/#/c/70141/ > >Those have not yet been merged so they may still change before being >merged. > >I don't know when such tests will show up in an actual official CTS >release, possibly not until the next major Android release. > > > _______________________________________________ Seandroid-list mailing list [email protected] To unsubscribe, send email to [email protected]. To get help, send an email containing "help" to [email protected].
