Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 156766 - implementatoin of setenforce 0 broken
Summary: implementatoin of setenforce 0 broken
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy-targeted
Version: 4
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Daniel Walsh
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2005-05-04 05:12 UTC by Jonathan S. Shapiro
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2005-05-06 00:36:40 UTC

Attachments (Terms of Use)

Description Jonathan S. Shapiro 2005-05-04 05:12:29 UTC

  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-06 00:36:40 UTC
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.