RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1391605 - Error when listing booleans from another store using semanage
Summary: Error when listing booleans from another store using semanage
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: policycoreutils
Version: 7.3
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Vit Mojzis
QA Contact: Milos Malik
URL:
Whiteboard:
Depends On: 1124345
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-03 15:44 UTC by Dalibor Pospíšil
Modified: 2019-08-06 13:00 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1124345
Environment:
Last Closed: 2019-08-06 13:00:15 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1391620 0 low CLOSED sepolicy does not list all booleans from another store 2021-02-22 00:41:40 UTC
Red Hat Product Errata RHBA-2019:2160 0 None None None 2019-08-06 13:00:23 UTC

Internal Links: 1391620

Description Dalibor Pospíšil 2016-11-03 15:44:23 UTC 
+++ This bug was initially created as a clone of Bug #1124345 +++

Description of problem:

If the other store contains a boolean which does not exist in the active policy semanage boolean -l produces an error.

This is caused by getting current statue for the boolean which actually does not exist in active policy.

Therefore I would propose to changes the output  of semanage boolean -l so it put e.g. '-' in the 'state' column if listing non-active store as it is misleading anyway.

# rpm -qa | grep -e selinux-policy -e policycoreutils
selinux-policy-devel-3.13.1-60.el7.noarch
selinux-policy-mls-3.13.1-102.el7.noarch
policycoreutils-newrole-2.5-9.el7.x86_64
policycoreutils-2.5-9.el7.x86_64
policycoreutils-devel-2.5-9.el7.x86_64
selinux-policy-3.13.1-102.el7.noarch
selinux-policy-targeted-3.13.1-102.el7.noarch
policycoreutils-python-2.5-9.el7.x86_64

# cat > mypolicy.cil << EOF
(boolean xyz false)
EOF

# semodule -i mypolicy.cil -s mls

# seinfo -b /etc/selinux/mls/policy/policy.30 | grep xyz
   xyz

# semanage boolean -l -S mls
...
irssi_use_full_network         (off  ,  off)  Allow the Irssi IRC Client to connect to any port, and to bind to any unreserved port.
mozilla_plugin_use_bluejeans   (off  ,  off)  Allow mozilla plugin to use Bluejeans.
OSError: No such file or directory
Comment 9 errata-xmlrpc 2019-08-06 13:00:15 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2019:2160
Note You need to log in before you can comment on or make changes to this bug.