-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 12/31/2013 12:20 PM, Chris Murphy wrote:
On Dec 31, 2013, at 8:57 AM, Daniel J Walsh dwalsh@redhat.com wrote:
THere was a bug in libselinux which is now fixed, that was causing the problem.
Right, but I thought that the bug caused the setting in /etc/selinux/config being ignored, while selinux=0 and enforcing=0 still worked?
Chris Murphy
Just back from break, and I believe that is the case. I am just beginning to dig into the problem.
selinux=0 should cause the kernel to not load SELinux LSM, which should keep selinux disabled. I guess the libselinux could still lie to the init and cause it to attempt a relabel.
Adam Williamson has put out a fixed libselinux-2.2.1-6.fc20, which should fix the problem.