Bug 1375126 - sesearch does not complain when non-existent boolean is provided on cmdline
Summary: sesearch does not complain when non-existent boolean is provided on cmdline
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: setools
Version: 7.3
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Vit Mojzis
QA Contact: Milos Malik
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-12 08:37 UTC by Milos Malik
Modified: 2019-02-27 13:54 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-02-27 13:54:51 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Milos Malik 2016-09-12 08:37:05 UTC
Description of problem:

Version-Release number of selected component (if applicable):
setools-console-3.3.8-1.1.el7.x86_64
setools-libs-3.3.8-1.1.el7.x86_64

How reproducible:
* always

Steps to Reproduce:
# getsebool xyz
Error getting active value for xyz
# seinfo -bxyz -x
ERROR: could not find datum for bool xyz
# sesearch -b xyz -A

# echo $?
0
# sesearch -b xyz -D

# echo $?
0
# sesearch -b xyz --auditallow

# echo $?
0
#

Actual results:
* sesearch does not produce any error message or error code

Expected results:
* sesearch produces an error message similar to getsebool or seinfo

Comment 1 Zdenek Pytela 2019-02-27 13:54:51 UTC
This issue was not selected to be included in Red Hat Enterprise Linux 7.7 because it is seen either as low or moderate impact to a small number of use-cases. The next release will be in Maintenance Support 1 Phase, which means that qualified Critical and Important Security errata advisories (RHSAs) and Urgent Priority Bug Fix errata advisories (RHBAs) may be released as they become available.

We will now close this issue, but if you believe that it qualifies for the Maintenance Support 1 Phase, please re-open; otherwise, we recommend moving the request to Red Hat Enterprise Linux 8 if applicable.


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