Bug 160883 - Bogous boolean allow_write_xhm
Bogous boolean allow_write_xhm
Product: Fedora
Classification: Fedora
Component: selinux-policy-strict (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Russell Coker
Depends On:
  Show dependency treegraph
Reported: 2005-06-17 19:13 EDT by Göran Uddeborg
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version: 1.25.4-10.1
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-03-27 00:45:02 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Göran Uddeborg 2005-06-17 19:13:40 EDT
Description of problem:
The file "booleans" contains a setting of a variable allow_write_xhm to true.
But the policy doesn't contain such a boolean.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.Boot with strict policy
Actual results:
A warning message about errors when the booleans are set.

Expected results:
No warning.

Additional info:
Maybe the intention was to set allow_write_xshm?
Comment 1 Daniel Walsh 2005-06-17 23:06:31 EDT
Fixed in selinux-policy-targeted-1.23.18-1
Comment 2 Danen Brücker 2005-06-30 20:46:20 EDT
(In reply to comment #1)
> Fixed in selinux-policy-targeted-1.23.18-1

Error still present in the strict policy package as reported initially.
Comment 3 Göran Uddeborg 2005-09-15 16:15:56 EDT
But hello?  This is a bug in the strict policy.  There hasn't been an "current
release" 1.25.4-10.1 of the strict policy.  There hasn't been any update at all
of the strict policy as far as I can see.

Was closing a mistake?  Or is the strict policy being abandoned and not supported?
Comment 4 Daniel Walsh 2005-09-16 10:52:24 EDT
Fixed in selinux-policy-strict-1.25.4-10.1

Strict is not being abandoned.  Sorry about not updating it.

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