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-minimum-3.7.19-54.el6_0.2.noarch
selinux-policy-doc-3.7.19-54.el6_0.2.noarch
selinux-policy-mls-3.7.19-54.el6_0.2.noarch
selinux-policy-3.7.19-54.el6_0.2.noarch
selinux-policy-targeted-3.7.19-54.el6_0.2.noarch

How reproducible:
always

Steps to Reproduce:
# matchpathcon /etc/sysconfig/iptables.save
/etc/sysconfig/iptables.save    system_u:object_r:etc_runtime_t:s0
# matchpathcon /etc/sysconfig/ip6tables.save
/etc/sysconfig/ip6tables.save   system_u:object_r:system_conf_t:s0

  
Actual results:
2 different contexts

Expected results:
the same context for both files

ip6tables.save file will be created with etc_runtime_t context. 

Both files should be created only by ip6?tables save script so the ip6tables.save file should have also etc_runtime_t context by default.

Milos,
good catch.

Fixed in selinux-policy-3.7.19-58.el6.

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