Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 650136

Summary: copy&paste errors in 'semanage boolean -l' output
Product: Red Hat Enterprise Linux 6 Reporter: Milos Malik <mmalik>
Component: selinux-policyAssignee: Miroslav Grepl <mgrepl>
Status: CLOSED ERRATA QA Contact: Milos Malik <mmalik>
Severity: low Docs Contact:
Priority: medium    
Version: 6.0CC: dwalsh
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: selinux-policy-3.7.19-64.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-05-19 11:56:57 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 Milos Malik 2010-11-05 10:52:06 UTC
Description of problem:


Version-Release number of selected component (if applicable):
policycoreutils-sandbox-2.0.83-19.1.el6.i686
policycoreutils-2.0.83-19.1.el6.i686
policycoreutils-newrole-2.0.83-19.1.el6.i686
policycoreutils-gui-2.0.83-19.1.el6.i686
policycoreutils-python-2.0.83-19.1.el6.i686

How reproducible:
always

Steps to Reproduce:
# semanage boolean -l | grep mod_auth_pam
allow_httpd_mod_auth_pam       -> off   Allow Apache to use mod_auth_pam
allow_httpd_mod_auth_ntlm_winbind -> off   Allow Apache to use mod_auth_pam
  
Actual results:
the description of allow_httpd_mod_auth_ntlm_winbind talks about mod_auth_pam

Expected results:
the description of allow_httpd_mod_auth_ntlm_winbind does not talk about mod_auth_pam

Comment 1 Milos Malik 2010-11-05 10:56:55 UTC
# semanage boolean -l | grep "fenced domain"
nagios_plugin_dontaudit_bind_port -> off   Allow fenced domain to connect to the network using TCP.
fenced_can_network_connect     -> off   Allow fenced domain to connect to the network using TCP.

Comment 3 Daniel Walsh 2010-11-05 11:50:40 UTC
Strange the second one does not exist in F15?

These boolean descriptions are defined in selinux-policy

Comment 4 Miroslav Grepl 2010-11-11 15:17:25 UTC
I will remove the "nagios_plugin_dontaudit_bind_port" boolean. Since the boolean is no longer necessary.

Comment 6 Miroslav Grepl 2010-12-09 16:09:44 UTC
Fixed in selinux-policy-3.7.19-59.el6

Comment 9 Miroslav Grepl 2011-01-14 15:15:37 UTC
Fixed in selinux-policy-3.7.19-64.el6

Comment 13 errata-xmlrpc 2011-05-19 11:56:57 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2011-0526.html