use this:Can someone help or explain please ..i can't set SELinux mode from enforcing to permissive mode ..why and how? Please help
https://forum.xda-developers.com/android/apps-games/isu-simple-app-to-deactivate-activate-t3478348
install the app(if you are using Lineage SU) and in controls of the app you can change kernel from enforcing to permissive
why?
''The purpose of supporting permissive policies is to allow a system to run with SELinux enabled, while still allowing all accesses that the applications are trying to do. A SELinux-enabled system that runs in permissive mode is not protected by SELinux. The true purpose is that it still logs what it would have denied and as such allows the administrator to get a sense of what would happen if he switches the system from permissive to enforcing mode.
Switching between enforcing and permissive mode is possible if the kernel you have booted supports SELinux Development mode (CONFIG_SECURITY_SELINUX_DEVELOP=y). Otherwise, the kernel automatically boots in enforcing mode and you are not able to switch back. Although such kernels are sometimes considered the safest (as a successful intrusion still doesn't allow the attacker to disable SELinux, even if he obtains full administrative access) most distributions keep development mode on. After all, once you have full administrative access, you can rebuild policies and add in the privileges you need anyhow. And even kernels with development mode on can still be hardened - there is a secure_mode_policyload boolean that disables switching to permissive mode until you reboot the system.
To get information about the current state, you can use getenforce or sestatus.''
in simple words, if you have a permissive kernel, all apps can do all they need to, as enforcing is not allowing things that could put the phone in security risk.
Permissive kernel is not passing safety net, so no games and apps that need it to work (PO GO, Mario, Bank Apps)
read more here:
https://wiki.gentoo.org/wiki/SELinux/Tutorials/Permissive_versus_enforcing
---------- Post added at 01:17 AM ---------- Previous post was at 12:56 AM ----------
I had the same problem in both roms, as you said.
I think the dev is aware of it and has made improvements in the kernel that are fixing that issue.
We must wait for a new build of the roms, or kernel release to be able to fix it.
Last edited:
