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.
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
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.
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