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 1271996 - No SELinux boolean to allow tmpwatch on samba_share_t or nfs_t
Summary: No SELinux boolean to allow tmpwatch on samba_share_t or nfs_t
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: selinux-policy
Version: 6.7
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Miroslav Grepl
QA Contact: Milos Malik
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-10-15 09:09 UTC by Eva Mrakova
Modified: 2019-10-28 13:30 UTC (History)
9 users (show)

Fixed In Version: selinux-policy-3.7.19-282.el6
Doc Type: Bug Fix
Doc Text:
Clone Of: 1218330
Environment:
Last Closed: 2016-05-10 20:02:05 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:0763 0 normal SHIPPED_LIVE selinux-policy bug fix update 2016-05-10 22:33:46 UTC

Description Eva Mrakova 2015-10-15 09:09:03 UTC 
Also present on RHEL6 for
selinux-policy-3.7.19-279.el6_7.6.noarch

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

Description of problem:
Right now running tmpwatch on directories being labelled as samba_share_t
or nfs_t leads to AVC denied messages, which might be right in the first
case but it should be possible to allow it via SELinux booleans through -
because we have backups on NFS that are cleaned up with tmpwatch or also
a samba share for temporary files being watched by tmpwatch. Both fails as
of writing due to the too strict SELinux policy.

Version-Release number of selected component (if applicable):
selinux-policy-targeted-3.13.1-23.el7.noarch
tmpwatch-2.11-5.el7.x86_64

How reproducible:
Everytime, label a directory with samba_share_t or nfs_t and run tmpwatch.

Actual results:
No SELinux boolean to allow tmpwatch on samba_share_t or nfs_t.

Expected results:
SELinux boolean to allow tmpwatch on samba_share_t or nfs_t.

Additional info:
type=AVC msg=audit(1430425770.447:23279): avc:  denied  { setattr } for  pid=19622 comm="tmpwatch" name="our-nfs-directory" dev="0:35" ino=40965 scontext=system_u:system_r:tmpreaper_t:s0-s0:c0.c1023 tcontext=system_u:object_r:nfs_t:s0 tclass=dir
type=SYSCALL msg=audit(1430425770.447:23279): arch=x86_64 syscall=utime success=no exit=EACCES a0=4042b7 a1=7fff4ea61d70 a2=7fb7d1c377b8 a3=7fff4ea61ac0 items=0 ppid=101823 pid=19622 auid=0 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=493 comm=tmpwatch exe=/usr/sbin/tmpwatch subj=system_u:system_r:tmpreaper_t:s0-s0:c0.c1023 key=(null)
Comment 4 errata-xmlrpc 2016-05-10 20:02:05 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-0763.html
Note You need to log in before you can comment on or make changes to this bug.