SELinux State Option is Not a Good Idea...
Hello There!
The SELinux State option really isn't a good idea, at least, as it is.
I know many individuals who used this option and it is causing a Bootloop or being stuck in Boot.
For a device to be able to change its SELinux State, it requires a Custom/Modified Kernel to be installed to work appropriately.
I would like to recommend that, if this option was kept in the app, it really needs an appropriate disclaimer with all the warnings.
I'm a developer myself and have developed The SELinux Switch App and am very knowledgeable about the Security Enhanced Linux (aka SELinux).
Thank you very much for your time and understanding with this.
~Ibuprophen
The SELinux State option really isn't a good idea, at least, as it is.
I know many individuals who used this option and it is causing a Bootloop or being stuck in Boot.
For a device to be able to change its SELinux State, it requires a Custom/Modified Kernel to be installed to work appropriately.
I would like to recommend that, if this option was kept in the app, it really needs an appropriate disclaimer with all the warnings.
I'm a developer myself and have developed The SELinux Switch App and am very knowledgeable about the Security Enhanced Linux (aka SELinux).
Thank you very much for your time and understanding with this.
~Ibuprophen
Sharing is caring, show love and share the thread with your friends.
In addition to just Bumping this post...
It would be great if there were some/any type of indication that the individual user would need to set the SELinux State to Permissive Mode.
It just seems like this option is available to the individual user but, nothing regarding whether or not this option is:
1) Just available to the user for convenience?
2) Is Needed/Required for a specific function within the Lucky Patcher app?
3) Is Needed/Required for 1 or more patches within the Lucky Patcher app?
It would be a great indicator for this option...
Thanks a bunch!
~Ibuprophen