Bug 734568
Summary: | postdrop causing avc failure | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Daniel Yeisley <dyeisley> |
Component: | selinux-policy | Assignee: | Miroslav Grepl <mgrepl> |
Status: | CLOSED ERRATA | QA Contact: | Milos Malik <mmalik> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 6.2 | CC: | dwalsh, mmalik |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | selinux-policy-3.7.19-109.el6 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2011-12-06 10:18:04 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Daniel Yeisley
2011-08-30 18:52:09 UTC
Is abrt sending out email via postfix? optional_policy(` abrt_rw_fifo_file(mta_user_agent) ') Miroslav I think we need. Looks so. Unintentionally reproduced by /CoreOS/selinux-policy/Regression/bz271561-corosync-and-similar ---- time->Wed Aug 31 08:18:58 2011 type=SYSCALL msg=audit(1314793138.223:54867): arch=c000003e syscall=5 success=no exit=-13 a0=2 a1=7fffcbb86320 a2=7fffcbb86320 a3=7fffcbb86050 items=0 ppid=29338 pid=29341 auid=0 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=90 sgid=90 fsgid=90 tty=(none) ses=807 comm="postdrop" exe="/usr/sbin/postdrop" subj=system_u:system_r:postfix_postdrop_t:s0-s0:c0.c1023 key=(null) type=AVC msg=audit(1314793138.223:54867): avc: denied { getattr } for pid=29341 comm="postdrop" path="pipe:[622070]" dev=pipefs ino=622070 scontext=system_u:system_r:postfix_postdrop_t:s0-s0:c0.c1023 tcontext=system_u:system_r:abrt_t:s0-s0:c0.c1023 tclass=fifo_file ---- Fixed in selinux-policy-3.7.19-109.el6 moving to verified; The original issue doesn't appear in RHEL6.2-20110907.1. 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-2011-1511.html |