Bug 1511437

Summary: more specific file context pattern for /run/ebtables.lock is missing
Product: Red Hat Enterprise Linux 7 Reporter: Milos Malik <mmalik>
Component: selinux-policyAssignee: Lukas Vrabec <lvrabec>
Status: CLOSED ERRATA QA Contact: Milos Malik <mmalik>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.5CC: lvrabec, mgrepl, mmalik, plautrba, redhat-airlock, ssekidde
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: selinux-policy-3.13.1-197.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-10-30 10:01:27 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Milos Malik 2017-11-09 11:23:18 UTC 
Description of problem:
# sesearch -s iptables_t -t var_run_t -T
Found 1 semantic te rules:
   type_transition iptables_t var_run_t : file iptables_var_run_t; 
# semanage fcontext -l | grep run/ebtables
#

Version-Release number of selected component (if applicable):
selinux-policy-3.13.1-177.el7.noarch
selinux-policy-sandbox-3.13.1-177.el7.noarch
selinux-policy-devel-3.13.1-177.el7.noarch
selinux-policy-doc-3.13.1-177.el7.noarch
selinux-policy-mls-3.13.1-177.el7.noarch
selinux-policy-minimum-3.13.1-177.el7.noarch
selinux-policy-targeted-3.13.1-177.el7.noarch

How reproducible:
* always

Steps to Reproduce:
# ls -Z /run/ebtables.lock 
-rw-------. root root system_u:object_r:iptables_var_run_t:s0 /run/ebtables.lock
# restorecon -v /run/ebtables.lock
restorecon reset /run/ebtables.lock context system_u:object_r:iptables_var_run_t:s0->system_u:object_r:var_run_t:s0
#

Actual results:
 * restorecon changes the label

Expected results:
 * restorecon does not change the label
Comment 3 Lukas Vrabec 2018-05-23 13:50:04 UTC 
*** Bug 1581613 has been marked as a duplicate of this bug. ***
Comment 7 errata-xmlrpc 2018-10-30 10:01:27 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.

https://access.redhat.com/errata/RHBA-2018:3111