Bug 1372705 - couple of interface definitions needed in selinux-policy [NEEDINFO]
Summary: couple of interface definitions needed in selinux-policy
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: selinux-policy
Version: 7.3
Hardware: All
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: Lukas Vrabec
QA Contact: Milos Malik
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-02 12:41 UTC by Lokesh Mandvekar
Modified: 2016-11-04 02:38 UTC (History)
8 users (show)

Fixed In Version: selinux-policy-3.13.1-97.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-04 02:38:29 UTC
Target Upstream Version:
ksrot: needinfo? (lsm5)


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:2283 0 normal SHIPPED_LIVE selinux-policy bug fix and enhancement update 2016-11-03 13:36:25 UTC

Description Lokesh Mandvekar 2016-09-02 12:41:28 UTC
Description of problem:

We'll need to include two interface definitions in selinux-policy for docker-selinux to build on rhel 7.3. Those are:

1. fs_rw_nsfs_files
2. virt_stub_svirt_sandbox_file

These have been included in docker-selinux as a temporary fix but would be great to have them in selinux-policy long term.

Version-Release number of selected component (if applicable): 
selinux-policy-3.13.1-93.el7.noarch

See: https://github.com/projectatomic/docker-selinux/issues/15

Comment 2 Lukas Vrabec 2016-09-02 15:01:29 UTC
We need to back port labeling for nsfs_t filesystem from fedora.

Comment 11 errata-xmlrpc 2016-11-04 02:38:29 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://rhn.redhat.com/errata/RHBA-2016-2283.html


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