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.
Previously, a secadm SELinux user was not allowed to modify SELinux configuration files. With this update, the relevant SELinux policy has been fixed and the secadm SELinux user can now modify these configuration files.
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
Previously, a secadm SELinux user was not allowed to modify SELinux configuration files. With this update, the relevant SELinux policy has been fixed and the secadm SELinux user can now modify these configuration files.
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
Description of problem: It seems that secadm_r doesn't have write permission to both default_context_t and selinux_config_t. I expected it would have write permission at least to selinux_config_t. [root/secadm_r/SystemLow@ntc242 ~]# sesearch --role_source secadm_r -s secadm_t -t selinux_config_t --allow Found 11 semantic av rules: allow secadm_usertype selinux_config_t : file { ioctl read getattr lock open } ; allow secadm_usertype selinux_config_t : dir { ioctl read getattr lock search open } ; allow secadm_usertype selinux_config_t : lnk_file { read getattr } ; allow secadm_t selinux_config_t : file { getattr relabelfrom relabelto } ; allow secadm_t selinux_config_t : dir { ioctl read getattr lock relabelfrom relabelto search open } ; allow secadm_t selinux_config_t : lnk_file { getattr relabelfrom relabelto } ; allow secadm_t selinux_config_t : chr_file { getattr relabelfrom relabelto } ; allow secadm_t selinux_config_t : blk_file { getattr relabelfrom relabelto } ; allow secadm_t selinux_config_t : sock_file { getattr relabelfrom relabelto } ; allow secadm_t selinux_config_t : fifo_file { getattr relabelfrom relabelto } ; allow secadm_usertype file_type : filesystem getattr ; [root/secadm_r/SystemLow@ntc242 ~]# Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: