Description of problem: I want to disble SElinux (Yes, I know you want selinux to be enabled...) and used two ways, but all of them were unsuccessfull, so selinux is still enabled. I tried: * SELINUX=disabled in /etc/selinux/config * system-config-selinux and select "Disabled". After a reboot, the system still is enabled: [root@frodo bubeck]# sestatus SELinux status: enabled SELinuxfs mount: /sys/fs/selinux SELinux root directory: /etc/selinux Loaded policy name: targeted Current mode: permissive Mode from config file: disabled Policy MLS status: enabled Policy deny_unknown status: allowed Max kernel policy version: 28 Version-Release number of selected component (if applicable): selinux-policy-3.12.1-106.fc20.noarch How reproducible: Always Steps to Reproduce: 1. Install FC20 2. set SELINUX=disabled in /etc/selinux/config 3. reboot 4. check with "sestatus" Actual results: SELinux status: enabled Expected results: SELinux status: disabled Additional info:
Same problem here. But the cause is probably libselinux and not selinux-policy. Description of problem: Fedora 20 host with selinux disabled After upgrading to libselinux-2.2.1-4.fc20, selinux will be enabled automatically and can not be disabled with /etc/selinux/config. Version-Release number of selected component (if applicable): libselinux-2.2.1-4.fc20 How reproducible: Steps to Reproduce: 1. Fedora 20 installation 2. Disable selinux via /etc/selinux/config 3. Upgrade to libselinux-2.2.1-4.fc20 4. After rebooting, selinux is enabled Actual results: [root@fc20 ~]# sestatus SELinux status: enabled SELinuxfs mount: /sys/fs/selinux SELinux root directory: /etc/selinux Loaded policy name: targeted Current mode: permissive Mode from config file: disabled Policy MLS status: enabled Policy deny_unknown status: allowed Max kernel policy version: 28 Expected results: SELinux status: disabled
Workaround: 1) Edit /etc/default/grub 2) Add selinux=0 to GRUB_CMDLINE_LINUX 3) grub2-mkconfig -o /boot/grub2/grub.cfg 4) reboot and selinux is disabled
*** Bug 1047045 has been marked as a duplicate of this bug. ***
Please check: https://bugzilla.redhat.com/show_bug.cgi?id=1046470 *** This bug has been marked as a duplicate of bug 1046470 ***