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.
Bug 1064326 - SELinux prevents logrotate from reading /var/log/core directory
Summary: SELinux prevents logrotate from reading /var/log/core directory
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: selinux-policy
Version: 6.5
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Lukas Vrabec
QA Contact: Milos Malik
URL:
Whiteboard:
: 1097400 (view as bug list)
Depends On:
Blocks: 1131460 1153333
TreeView+ depends on / blocked
 
Reported: 2014-02-12 12:36 UTC by Milos Malik
Modified: 2014-10-15 19:21 UTC (History)
3 users (show)

Fixed In Version: selinux-policy-3.7.19-249.el6
Doc Type: Bug Fix
Doc Text:
Clone Of: 1064322
: 1153333 (view as bug list)
Environment:
Last Closed: 2014-10-14 08:00:06 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2014:1568 0 normal SHIPPED_LIVE selinux-policy bug fix and enhancement update 2014-10-14 01:27:37 UTC

Description Milos Malik 2014-02-12 12:36:20 UTC 
Description of problem:
 * vdsm package contains a cronjob which runs logrotate each hour and the logrotate job wants to access *.dump files in /var/log/core directory

Version-Release number of selected component (if applicable):
selinux-policy-3.7.19-231.el6.noarch
selinux-policy-doc-3.7.19-231.el6.noarch
selinux-policy-minimum-3.7.19-231.el6.noarch
selinux-policy-mls-3.7.19-231.el6.noarch
selinux-policy-targeted-3.7.19-231.el6.noarch
vdsm-4.13.0-23.1.el6rhs.x86_64

How reproducible:
each hour

Steps to Reproduce:
1) install vdsm package together with its dependencies
2) make sure that crond is running
3) wait for an hour or force the logrotate job to start

Actual results (enforcing mode):
----
type=PATH msg=audit(02/12/2014 12:01:01.799:857) : item=0 name=/var/log/core inode=61398 dev=fc:03 mode=dir,sticky,777 ouid=root ogid=root rdev=00:00 obj=system_u:object_r:virt_cache_t:s0 nametype=NORMAL 
type=CWD msg=audit(02/12/2014 12:01:01.799:857) :  cwd=/ 
type=SYSCALL msg=audit(02/12/2014 12:01:01.799:857) : arch=x86_64 syscall=open success=no exit=-13(Permission denied) a0=7fff8acc33b0 a1=90800 a2=f1a73e a3=25 items=1 ppid=20006 pid=20008 auid=root uid=root gid=root euid=root suid=root fsuid=root egid=root sgid=root fsgid=root tty=(none) ses=109 comm=logrotate exe=/usr/sbin/logrotate subj=system_u:system_r:logrotate_t:s0-s0:c0.c1023 key=(null) 
type=AVC msg=audit(02/12/2014 12:01:01.799:857) : avc:  denied  { read } for  pid=20008 comm=logrotate name=core dev=vda3 ino=61398 scontext=system_u:system_r:logrotate_t:s0-s0:c0.c1023 tcontext=system_u:object_r:virt_cache_t:s0 tclass=dir 
----

Expected results:
 * no AVCs
Comment 1 Milos Malik 2014-02-18 13:57:15 UTC 
No matter when bz#1066407 gets fixed, the /var/log/core directory should be labeled virt_log_t.
Comment 2 Daniel Walsh 2014-02-21 20:41:37 UTC 
 sesearch -T | grep virt_cache_t
   type_transition svirt_tcg_t var_t : file virt_cache_t; 
   type_transition svirt_t var_t : file virt_cache_t; 
   type_transition svirt_tcg_t var_t : dir virt_cache_t; 
   type_transition svirt_t var_t : dir virt_cache_t; 

THe only way I now of create a virt_cache_t dir would be via a filetrans rule from a var_t, could /var/log have been mislabeled as var_t rather then var_log_t?
Comment 3 Milos Malik 2014-02-24 09:05:11 UTC 
The problem is in the package, it brings own labeling pattern (see also bz#1066407):

# rpm -q --scripts vdsm | grep semanage
    /usr/sbin/semanage fcontext -a -t virt_cache_t '/var/log/core(/.*)?'
#
Comment 4 Daniel Walsh 2014-02-24 16:55:38 UTC 
Ok.
Comment 5 Daniel Walsh 2014-05-17 10:53:18 UTC 
*** Bug 1097400 has been marked as a duplicate of this bug. ***
Comment 9 errata-xmlrpc 2014-10-14 08:00:06 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.

http://rhn.redhat.com/errata/RHBA-2014-1568.html
Note You need to log in before you can comment on or make changes to this bug.