On 03/25/2013 12:49 PM, William Roberts wrote:
Make sure to set system_app_manage to true on the booleans screen
before going to enforcing mode.
Only necessary for using SEAndroidManager, which we no longer
include/build by default. For SEAndroidAdmin, you only need
manage_selinux boolean (which is enabled by default).
On Mon, Mar 25, 2013 at 8:38 AM, rpcraig <[email protected]> wrote:
On 03/25/2013 11:22 AM, Ronan TROTIN wrote:
Hi
I'm new to seandroid topics and i need to implement it on a platform.
I have just synced aosp (master) and seandroid like described on the
wiki (http://selinuxproject.org/page/SEAndroid) and started tests in the
emulator to understand how it works.
I tried "setenforce Enforcing" form adb i'm now unable to
getenforce/setenforce.
is that the expected behavior?
--
This message was distributed to subscribers of the seandroid-list mailing
list.
If you no longer wish to subscribe, send mail to [email protected]
with
the words "unsubscribe seandroid-list" without quotes as the message.
Yes, this is expected behaviour. Use the SEAndmin app to toggle back to
permissive mode.
--
This message was distributed to subscribers of the seandroid-list mailing
list.
If you no longer wish to subscribe, send mail to [email protected]
with
the words "unsubscribe seandroid-list" without quotes as the message.
--
This message was distributed to subscribers of the seandroid-list mailing list.
If you no longer wish to subscribe, send mail to [email protected] with
the words "unsubscribe seandroid-list" without quotes as the message.
