Hide Forgot
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.
Some of these are already fixed in F15 and I am fixing others in F15 and will fix in RHEL6.2.
Fixed in selinux-policy-3.7.19-98.el6
What is wrong? I don't see it.
Fixed in selinux-policy-3.7.19-107.el6
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