What type of build is it? user builds call setenforce(1) from init.cpp no matter what. Only userdebug and eng builds respect the androidboot.selinux mode when init imports the kernel command line.
I've never actually done this with the VM though, only actual devices, so I don't know if its different in practice. On Mon, May 23, 2016 at 9:50 AM, Edward Paul Ratazzi <[email protected]> wrote: > I am using an Android 5.1.1 x86 VM in VirtualBox which was built with > SELinux in disabled mode (per getenforce). The SELinux infrastructure > files such as sepolicy, seapp_contexts, etc. are present in the image. I > would like to know if there is a way to enable SELinux on this this VM > without rebuilding it (I already know how to do that). > > > I have tried passing enforcing=0 and androidboot.selinux=permissive on > the kernel command line (by way of grub.cfg) and verified by way of dmesg > inside the VM that these parameters are reaching the VM during boot. > Unfortunately, this has had no effect on the state of SELinux in the VM. > > > Is what I'm trying to do possible, and if so, what may I be missing? > > > Thank you. > > > _______________________________________________ > Seandroid-list mailing list > [email protected] > To unsubscribe, send email to [email protected]. > To get help, send an email containing "help" to > [email protected]. > -- Respectfully, William C Roberts
_______________________________________________ Seandroid-list mailing list [email protected] To unsubscribe, send email to [email protected]. To get help, send an email containing "help" to [email protected].
