Bug 1311606 - RFE: Add strict domain for confining virtlogd daemon
Summary: RFE: Add strict domain for confining virtlogd daemon
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
medium
Target Milestone: rc
: ---
Assignee: Lukas Vrabec
QA Contact: Milos Malik
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-24 15:13 UTC by Daniel Berrangé
Modified: 2016-11-04 02:43 UTC (History)
9 users (show)

Fixed In Version: selinux-policy-3.13.1-87.el7
Doc Type: Enhancement
Doc Text:
Clone Of: 1311576
Environment:
Last Closed: 2016-11-04 02:43:36 UTC
Target Upstream Version:


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 Daniel Berrangé 2016-02-24 15:13:09 UTC
libvirt in RHEL-7.3 is rebasing to version 1.3.1, so we'll want this upstream policy enhancement pulled into RHEL 7.3 too

+++ This bug was initially created as a clone of Bug #1311576 +++

Description of problem:
The virtlogd daemon is currently given the same context as
libvirtd. This is essentially unrestricted host access which
is not at all desirable. The virtlogd daemon is a small single
purpose daemon whose only job is logging. It should have a
dedicated context which strictly controls what it is permitted
todo.

I have written a policy that can do this and submitted upstream

  https://github.com/fedora-selinux/selinux-policy/pull/103

Comment 8 errata-xmlrpc 2016-11-04 02:43:36 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.