Created attachment 671369 [details] sendmail policy generated by iteratively silencing SELinux AVC denials for sendmail.sendmail Description of problem: When sendmail is invoked from other programs, multiple SELinux AVC denials occur. The scenario: nginx configured operate in conjunction with php-fpm The problem: Whenever a program attempts to invoke sendmail.sendmail it causes SELinux denials to occur. Typically this is due to: 1) nginx log rotation failure due to a SELinux AVC denial (already reported) 2) php-fpm attempting to send e-mail from web applications Version-Release number of selected component (if applicable): selinux-policy-targeted-3.11.1-67.fc18.noarch How reproducible: Every time. Steps to Reproduce: 1. Install and configure nginx and php-fpm 2. Run a web application that sends e-mail and allow nginx log file rotation 3. Observe AVC denials reported by SELinux Troubleshooter Actual results: There are a few sebools that can aid this problem e.g. httpd_can_sendmail which go part of the way but I found it necessary to repeatedly update a sendmail policy to quash all the denials. My sendmail.te is attached. Expected results: SELinux Troubleshooter should not report AVC denials under this usage scenario Additional info: Please excuse any ignorance of SELinux policy manipulation on my part. I am new to this and have since learned that using sendmail as my policy name might not have been a great idea but, for now, it works.
Ok, the problem is there is unlabeled process. Could you restart php-fpm service and see if it works then?
This system is a development netbook so php-fpm had been restarted many times. I think setting the sebool httpd_can_sendmail helped (php-fpm runs as user apache) but these errors also occurred when cron attempted to send nginx log rotation failure emails (by invoking sendmail indirectly through mail). SELinux Troubleshooter remains quiet now with the changes I had made in sendmail policy and setting that sebool. If you want me to undo some changes and retest I will be happy to follow and instructions you provide.
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. 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 '18'. 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 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. 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.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.