Bug 1601863 - /etc/selinux/targeted/contexts/customizable_types not including 'container_file_t'
Summary: /etc/selinux/targeted/contexts/customizable_types not including 'container_fi...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: selinux-policy
Version: 7.6
Hardware: All
OS: Linux
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Lukas Vrabec
QA Contact: Milos Malik
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-07-17 10:56 UTC by Lukas Vrabec
Modified: 2018-10-30 10:08 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-10-30 10:07:41 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:3111 None None None 2018-10-30 10:08:12 UTC

Description Lukas Vrabec 2018-07-17 10:56:46 UTC
Description of problem:

/etc/selinux/targeted/context/customizable_types not including 'container_file_t':
Relates to /etc/selinux/targeted/context/customizable_types never having been updated to include 'container_file_t'. As such, when a user runs restorecon on a file or directory that had its SELinux security context changed to 'container_file_t' using chcon (instead of semanage), the label will change. Since 'svirt_sandbox_file_t' was included within /etc/selinux/targeted/context/customizable_types, restorecon would not change the old label.

Fix:

diff --git a/customizable_types b/customizable_types
index feaea3584..b3f6cb087 100644
--- a/customizable_types
+++ b/customizable_types
@@ -1,3 +1,4 @@
+container_file_t
 sandbox_file_t
 svirt_image_t
 svirt_home_t

Comment 6 errata-xmlrpc 2018-10-30 10:07:41 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


Note You need to log in before you can comment on or make changes to this bug.