Bug 883584 - SELinux Adminastration - not possible to set SELINUX=enforcing again
Summary: SELinux Adminastration - not possible to set SELINUX=enforcing again
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: policycoreutils
Version: 18
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Daniel Walsh
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-12-04 22:42 UTC by Flóki Pálsson
Modified: 2013-01-11 23:30 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-01-11 23:30:11 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Flóki Pálsson 2012-12-04 22:42:20 UTC
Description of problem:
It is not possible to set system default enforcing mode  SELINUX=enforcing from SELINUX=permissive with s-c-selinux.

Version-Release number of selected component (if applicable):
policycoreutils-gui-2.1.13-37.fc18.x86_64

How reproducible:
always

Steps to Reproduce:
1. with s-c-selinux set SELINUX=permissive
2. change with s-c-selinux back to enforcing
3. reboot 

  
Actual results:
System is in SELINUX=permissive mode.

Expected results:
System is in SELINUX=enforcing mode.

Additional info:
after step 2 then 
$ cat /etc/selinux/config
# This file controls the state of SELinux on the system.
# SELINUX= can take one of these three values:
#	enforcing - SELinux security policy is enforced.
#	permissive - SELinux prints warnings instead of enforcing.
#	disabled - SELinux is fully disabled.
SELINUX=permissive
# SELINUXTYPE= type of policy in use. Possible values are:
#	targeted - Only targeted network daemons are protected.
#	strict - Full SELinux protection.
SELINUXTYPE=targeted

changing in /etc/selinux/config 
SELINUX=permissive to SELINUX=enforcing works

This is possible in F17

Comment 1 Daniel Walsh 2012-12-06 19:41:59 UTC
Fixed in policycoreutils-2.1.13-44.fc18

Comment 2 Flóki Pálsson 2012-12-08 18:58:50 UTC
>Fixed in policycoreutils-2.1.13-44.fc18
Works.

Comment 3 Fedora Update System 2012-12-17 19:16:50 UTC
policycoreutils-2.1.13-46.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/policycoreutils-2.1.13-46.fc18

Comment 4 Fedora Update System 2012-12-18 21:28:40 UTC
Package policycoreutils-2.1.13-46.fc18:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing policycoreutils-2.1.13-46.fc18'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-20585/policycoreutils-2.1.13-46.fc18
then log in and leave karma (feedback).

Comment 5 Fedora Update System 2013-01-11 23:30:13 UTC
policycoreutils-2.1.13-46.fc18 has been pushed to the Fedora 18 stable repository.  If problems still persist, please make note of it in this bug report.


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