Bug 156766 - implementatoin of setenforce 0 broken
implementatoin of setenforce 0 broken
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: selinux-policy-targeted (Show other bugs)
4
All Linux
medium Severity medium
: ---
: ---
Assigned To: Daniel Walsh
: Security
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-05-04 01:12 EDT by Jonathan S. Shapiro
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-05-05 20:36:40 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 Jonathan S. Shapiro 2005-05-04 01:12:29 EDT
problem:

  setenforce 0 does not fully disable selinux

repeat by:

  create an empty directory somewhere, say, /mumble
  setenforce 0
  yum --installroot=/mumble groupinstall Base

watch all of the postinstall scripts fail

Which begs the question: why does selinux mishandle chroot environments this way
(subject of another bug report).
Comment 1 Jonathan S. Shapiro 2005-05-05 20:36:40 EDT
I have a better understanding of what was happening with this example, and I
think the bug should be closed. Certainly, it's not high priority. I'm closing
it accordingly.

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