Bug 154121 - selinux policy is (wrongly) set to enforcing
selinux policy is (wrongly) set to enforcing
Status: CLOSED WONTFIX
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: anaconda (Show other bugs)
4.0
All Linux
medium Severity medium
: ---
: ---
Assigned To: Anaconda Maintenance Team
Mike McLean
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-04-07 12:54 EDT by Kaj J. Niemi
Modified: 2007-11-30 17:07 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-04-12 13:42:04 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Kaj J. Niemi 2005-04-07 12:54:50 EDT
Description of problem:
If one drops system-config-securitylevel-tui from %%packages and the selinux
parameter is set to --disabled (or anything, really) the install is completes
but selinux is set to enforcing.

It seems like anaconda calls /usr/sbin/lokkit to set the selinux level and
policy to be used. An error (which scrolls by really fast) is printed out on vty 5.

It would be nice if for RHEL4 U1 system-config-securitylevel-tui was pulled as a
dependency every time, I spent a 3-4 hours chasing this down. :>

How reproducible:
Always

Steps to Reproduce:
Create a kickstart file specifying "selinux --disabled"
and mark system-config-securitylevel-tui as a non-installable package in %%packages.


Thanks. :-)
Comment 1 Jeremy Katz 2005-04-12 13:42:04 EDT
The problem is that people also want to not have to install
system-config-securitylevel-tui.  And it's not practical to replicate the setup
(especially as it changes over time).

Not installing system-config-securitylevel-tui is like not installing authconfig
or shadow-utils or a utility like that.
Comment 2 Kaj J. Niemi 2005-04-12 13:53:19 EDT
Yeah, I know. I'm one of those people who do not want
system-config-securitylevel-tui around. But the point was that if you install
w/o it the policy gets set to enforcing no matter what you specify in the
kickstart config.

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