Bug 195850

Summary:	setsebool/getsebool have inconsistent input and output values
Product:	[Fedora] Fedora	Reporter:	Hans Ulrich Niedermann <rhbugs>
Component:	policycoreutils	Assignee:	Daniel Walsh <dwalsh>
Status:	CLOSED RAWHIDE	QA Contact:	Ben Levenson <benl>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	5	CC:	dwalsh, pgraner
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2006-06-19 14:29:55 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Hans Ulrich Niedermann 2006-06-18 20:03:06 UTC

Description of problem:

  "getsebool" prints the bools as being "on" or "off", but "setsebool" only
accepts the values "false" (aka "0") and "true" (aka "1").

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

  policycoreutils-1.30.10-2.fc5

Steps to Reproduce:
1. Run "getsebool allow_execstack".
2. Read "allow_execstack --> on" (or "off").
3. Run "setsebool allow_execstack=on" (or "off") to set it to the very same
value the bool already has.
  
Actual results:

  setsebool: illegal value on for boolean allow_execstack

Expected results:

  <nothing>
  
  setsebool should just quietly set the value.

Comment 1 Daniel Walsh 2006-06-19 14:29:55 UTC

Fixed in policycoreutils-1.30.14-2 in rawhide.  This will be backported to FC5
if we need to update policycoreutils in the future.  Not worth doing it for this
minor change.