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 701885 - typo errors in 'semanage boolean -l' output
Summary: typo errors in 'semanage boolean -l' output
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: selinux-policy
Version: 6.1
Hardware: All
OS: Linux
low
low
Target Milestone: rc
: ---
Assignee: Miroslav Grepl
QA Contact: Milos Malik
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-04 07:52 UTC by Milos Malik
Modified: 2012-10-16 12:26 UTC (History)
2 users (show)

Fixed In Version: selinux-policy-3.7.19-112.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-12-06 10:07:38 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2011:1511 0 normal SHIPPED_LIVE selinux-policy bug fix and enhancement update 2011-12-06 00:39:17 UTC

Description Milos Malik 2011-05-04 07:52:20 UTC 
Description of problem:


Version-Release number of selected component (if applicable):
selinux-policy-3.7.19-93.el6.noarch
selinux-policy-doc-3.7.19-93.el6.noarch
selinux-policy-mls-3.7.19-93.el6.noarch
selinux-policy-minimum-3.7.19-93.el6.noarch
selinux-policy-targeted-3.7.19-93.el6.noarch

How reproducible:
always

unprived vs. unprivileged
================
# semanage boolean -l | grep unprived
sepgsql_enable_users_ddl       -> on    Allow unprived users to execute DDL statement

excessive characters ")
===============
# semanage boolean -l | grep shlib
allow_execmod                  -> on    Allow all unconfined executables to use libraries requiring text relocation that are not labeled textrel_shlib_t")
# semanage boolean -l | grep bugzilla\"
allow_execmem                  -> on    Allow unconfined executables to map a memory region as both executable and writable, this is dangerous and the executable should be reported in bugzilla")
allow_execstack                -> on    Allow unconfined executables to make their stack executable.  This should never, ever be necessary. Probably indicates a badly coded executable, but could indicate an attack. This executable should be reported in bugzilla")

Alow, Pupper vs. Allow, Puppet
===================
# semanage boolean -l | grep Alow
puppetmaster_use_db            -> off   Alow Pupper master to use connect to mysql and postgresql database
Comment 1 Milos Malik 2011-05-04 08:42:31 UTC 
postgres vs. postgreSQL vs. postgresql
=========================
# semanage boolean -l | grep postgres
exim_can_connect_db            -> off   Allow exim to connect to databases (postgres, mysql)
allow_user_postgresql_connect  -> off   Allow users to connect to PostgreSQL
puppetmaster_use_db            -> off   Alow Pupper master to use connect to mysql and postgresql database

It would be nice if we chose one of the 3 possibilities.
Comment 2 Miroslav Grepl 2011-05-04 14:19:53 UTC 
Some of these are already fixed in F15 and I am fixing others in F15 and will fix in RHEL6.2.
Comment 3 Miroslav Grepl 2011-06-14 14:07:16 UTC 
Fixed in selinux-policy-3.7.19-98.el6
Comment 6 Miroslav Grepl 2011-07-26 15:10:37 UTC 
What is wrong? I don't see it.
Comment 9 Miroslav Grepl 2011-08-10 15:29:51 UTC 
Fixed in selinux-policy-3.7.19-107.el6
Comment 16 errata-xmlrpc 2011-12-06 10:07:38 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.

http://rhn.redhat.com/errata/RHBA-2011-1511.html
Note You need to log in before you can comment on or make changes to this bug.