Bug 1047045 - F20 - Kernel update turns on SELINUX - Cannot deactivate
Summary: F20 - Kernel update turns on SELINUX - Cannot deactivate
Keywords:
Status: CLOSED DUPLICATE of bug 1046450
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 20
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-28 17:26 UTC by Gerald Cox
Modified: 2013-12-28 18:46 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-12-28 18:46:06 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Gerald Cox 2013-12-28 17:26:47 UTC
Description of problem:

Installed kernel in updates-testing repository.  After installation, filesystem was relabeled with SELINUX enabled even though selinux config specifies disabled.  As you can see from the sestatus command, SELinux shows enabled while mode from config file is disabled.  I tried rebooting to previous kernel, but can't turn it off now.    

/usr/sbin/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):
kernel-3.12.6-300.fc20


How reproducible:
Install kernel-3.12.6-300.fc20


Steps to Reproduce:
1.  dnf upgrade --enablerepo=updates-testing kernel*


Actual results:
SELinux enabled, even though configuration indicates disabled


Expected results:
SELinux configuration file determines whether or not SELinux is enabled

Additional info:

Comment 1 Gerald Cox 2013-12-28 18:46:06 UTC

*** This bug has been marked as a duplicate of bug 1046450 ***


Note You need to log in before you can comment on or make changes to this bug.