Summary: SELinux is preventing /usr/sbin/sendmail.sendmail "setsched" access. Detailed Description: SELinux denied access requested by sendmail. It is not expected that this access is required by sendmail and this access may signal an intrusion attempt. It is also possible that the specific version or configuration of the application is causing it to require additional access. Allowing Access: You can generate a local policy module to allow this access - see FAQ (http://docs.fedoraproject.org/selinux-faq-fc5/#id2961385) Please file a bug report. Additional Information: Source Context unconfined_u:system_r:sendmail_t:s0 Target Context unconfined_u:system_r:sendmail_t:s0 Target Objects None [ process ] Source sendmail Source Path /usr/sbin/sendmail.sendmail Port <Unknown> Host (removed) Source RPM Packages sendmail-8.14.3-8.fc12 Target RPM Packages Policy RPM selinux-policy-3.6.32-78.fc12 Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Plugin Name catchall Host Name (removed) Platform Linux (removed) 2.6.31.12-174.2.3.fc12.i686 #1 SMP Mon Jan 18 20:22:46 UTC 2010 i686 i686 Alert Count 2 First Seen Mon 08 Feb 2010 10:43:48 PM EST Last Seen Mon 08 Feb 2010 10:49:18 PM EST Local ID e7b819fa-a0cc-4cad-bb0f-d716b11c26d7 Line Numbers Raw Audit Messages node=(removed) type=AVC msg=audit(1265687358.419:37498): avc: denied { setsched } for pid=10932 comm="sendmail" scontext=unconfined_u:system_r:sendmail_t:s0 tcontext=unconfined_u:system_r:sendmail_t:s0 tclass=process node=(removed) type=SYSCALL msg=audit(1265687358.419:37498): arch=40000003 syscall=97 success=no exit=-13 a0=0 a1=0 a2=9 a3=ffffffc8 items=0 ppid=9320 pid=10932 auid=18183 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=485 sgid=485 fsgid=485 tty=(none) ses=6 comm="sendmail" exe="/usr/sbin/sendmail.sendmail" subj=unconfined_u:system_r:sendmail_t:s0 key=(null) Hash String generated from selinux-policy-3.6.32-78.fc12,catchall,sendmail,sendmail_t,sendmail_t,process,setsched audit2allow suggests: #============= sendmail_t ============== allow sendmail_t self:process setsched;
thinking of high-level potential reasons why I'm seeing this...early production stages of getting a cyrus mail server going on Fedora 12. Includes MailScanner (sorry), clamd; default mailer is MAILER(cyrusv2). Alerts happen on send of outgoing mail + incoming, so I doubt it's a unique codepath due to the local mailer. Thanks for having a look!
I have never seen this before, but I see it with other mailers, so I guess we should allow it. Miroslov can you add this access.
Fixed in selinux-policy-3.6.32-86.fc12
Cool, thanks! Watching http://koji.fedoraproject.org/koji/packageinfo?packageID=32 I'm relatively new to selinux; had you denied this, what would I do make a local change to enable this syscall? I'm just not "getting it" from the guides, which focus on file contexts.
You can add these rules for now using # grep avc /var/log/audit/audit.log | audit2allow -M mypol # semodule -i mypol.pp
many thanks for your patience. I grepped just the particular avc, it seems 'semodule -i' is persistent across reboots, and I should 'semodule -d mypol' when selinux-policy is actually updated. Good stuff, selinux!
selinux-policy-3.6.32-86.fc12 solves this issue. Thanks! You might want to make a note in the changelog, though. [continuing above, better to 'semodule -r mypol' to remove policy, not just disable.]
selinux-policy-3.6.32-89.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/selinux-policy-3.6.32-89.fc12
selinux-policy-3.6.32-89.fc12 has been pushed to the Fedora 12 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update selinux-policy'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F12/FEDORA-2010-1836
selinux-policy-3.6.32-89.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report.