Bug 249149
Summary: | SELinux prevents Postfix from accessing anon_inode:[eventpoll] | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Anthony Messina <amessina> |
Component: | selinux-policy-targeted | Assignee: | Daniel Walsh <dwalsh> |
Status: | CLOSED WONTFIX | QA Contact: | Ben Levenson <benl> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 7 | CC: | jk, triage, wahjava |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-06-17 01:56: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
Anthony Messina
2007-07-21 14:33:48 UTC
Added definition for anon_inodefs in selinux-policy-targeted-2.6.4-29.fc7 *** Bug 249205 has been marked as a duplicate of this bug. *** *** Bug 249206 has been marked as a duplicate of this bug. *** *** Bug 249207 has been marked as a duplicate of this bug. *** "Added definition for anon_inodefs in selinux-policy-targeted-2.6.4-29.fc7" is not enough: #audit2allow -m temppostfix -a -l module temppostfix 1.0; require { type procmail_t; type postfix_pickup_t; type anon_inodefs_t; type postfix_qmgr_t; type postfix_smtpd_t; type postfix_local_t; type postfix_cleanup_t; class file { read write }; } #============= postfix_cleanup_t ============== allow postfix_cleanup_t anon_inodefs_t:file { read write }; #============= postfix_local_t ============== allow postfix_local_t anon_inodefs_t:file { read write }; #============= postfix_pickup_t ============== allow postfix_pickup_t anon_inodefs_t:file { read write }; #============= postfix_qmgr_t ============== allow postfix_qmgr_t anon_inodefs_t:file { read write }; #============= postfix_smtpd_t ============== allow postfix_smtpd_t anon_inodefs_t:file { read write }; #============= procmail_t ============== allow procmail_t anon_inodefs_t:file { read write }; is needed to stop selinux from complaining OK, bounce is also concerned: module temppostfix 1.0; require { type procmail_t; type postfix_pickup_t; type anon_inodefs_t; type postfix_qmgr_t; type postfix_smtpd_t; type postfix_smtp_t; type postfix_local_t; type postfix_cleanup_t; type postfix_bounce_t; class file { read write }; } #============= postfix_cleanup_t ============== allow postfix_cleanup_t anon_inodefs_t:file { read write }; #============= postfix_local_t ============== allow postfix_local_t anon_inodefs_t:file { read write }; #============= postfix_pickup_t ============== allow postfix_pickup_t anon_inodefs_t:file { read write }; #============= postfix_qmgr_t ============== allow postfix_qmgr_t anon_inodefs_t:file { read write }; #============= postfix_smtpd_t ============== allow postfix_smtpd_t anon_inodefs_t:file { read write }; #============= procmail_t ============== allow procmail_t anon_inodefs_t:file { read write }; #============= postfix_bounce_t ============== allow postfix_bounce_t anon_inodefs_t:file { read write }; #============= postfix_smtp_t ============== allow postfix_smtp_t anon_inodefs_t:file { read write }; selinux-policy-targeted-2.6.4-30.fc7 WORKSFORME for the postfix part but I still have the procmail denial: require { type anon_inodefs_t; type procmail_t; class file { read write }; } #============= procmail_t ============== allow procmail_t anon_inodefs_t:file { read write }; Should I open a procmail bug for this one? No that will be fixed in selinux-policy-2.6.4-34 This bug exists again in selinux-policy-targeted-2.6.4-46.fc7 userid 48 is apache on this machine. avc: denied { read, write } for comm="sendmail" dev=anon_inodefs egid=48 euid=48 exe="/usr/sbin/sendmail.postfix" exit=0 fsgid=48 fsuid=48 gid=48 items=0 name="[eventpoll]" path="anon_inode:[eventpoll]" pid=6494 scontext=system_u:system_r:system_mail_t:s0 sgid=48 subj=system_u:system_r:system_mail_t:s0 suid=48 tclass=file tcontext=system_u:object_r:anon_inodefs_t:s0 tty=(none) uid=48 That is strange I am looking at the selinux-policy-2.6.4-48 policy and it seems to be there. Please test this package. Available in Fedora-Testing. With that release, I do not get this error in enforcing mode. As far as I am concerned, selinux-policy-targeted-2.6.4-46.fc7 works for me. I do not need additional rules. This message is a reminder that Fedora 7 is nearing the end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 7. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '7'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 7's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 7 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. If possible, it is recommended that you try the newest available Fedora distribution to see if your bug still exists. Please read the Release Notes for the newest Fedora distribution to make sure it will meet your needs: http://docs.fedoraproject.org/release-notes/ The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Fedora 7 changed to end-of-life (EOL) status on June 13, 2008. Fedora 7 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. |