Description of problem: SELinux is preventing /usr/sbin/sendmail.sendmail from using the 'net_admin' capabilities. ***** Plugin catchall (100. confidence) suggests *************************** If you believe that sendmail.sendmail should have the net_admin capability by default. Then you should report this as a bug. You can generate a local policy module to allow this access. Do allow this access for now by executing: # grep newaliases /var/log/audit/audit.log | audit2allow -M mypol # semodule -i mypol.pp Additional Information: Source Context unconfined_u:system_r:system_mail_t:s0-s0:c0.c1023 Target Context unconfined_u:system_r:system_mail_t:s0-s0:c0.c1023 Target Objects [ capability ] Source newaliases Source Path /usr/sbin/sendmail.sendmail Port <Unknown> Host (removed) Source RPM Packages sendmail-8.14.5-15.fc18.x86_64 sendmail-8.14.7-1.fc18.x86_64 Target RPM Packages Policy RPM selinux-policy-3.11.1-66.fc18.noarch selinux- policy-3.11.1-97.fc18.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 3.6.10-4.fc18.x86_64 #1 SMP Tue Dec 11 18:01:27 UTC 2012 x86_64 x86_64 Alert Count 1 First Seen 2013-06-18 19:43:18 CEST Last Seen 2013-06-18 19:43:18 CEST Local ID 5fdcad87-35a3-4ad8-bdcc-13c02514d731 Raw Audit Messages type=AVC msg=audit(1371577398.968:355): avc: denied { net_admin } for pid=10361 comm="newaliases" capability=12 scontext=unconfined_u:system_r:system_mail_t:s0-s0:c0.c1023 tcontext=unconfined_u:system_r:system_mail_t:s0-s0:c0.c1023 tclass=capability type=SYSCALL msg=audit(1371577398.968:355): arch=x86_64 syscall=ioctl success=no exit=ENODEV a0=4 a1=8933 a2=7fff512a61e0 a3=1c items=0 ppid=10359 pid=10361 auid=1000 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=51 sgid=51 fsgid=51 tty=pts0 ses=2 comm=newaliases exe=/usr/sbin/sendmail.sendmail subj=unconfined_u:system_r:system_mail_t:s0-s0:c0.c1023 key=(null) Hash: newaliases,system_mail_t,system_mail_t,capability,net_admin Additional info: reporter: libreport-2.1.9 hashmarkername: setroubleshoot kernel: 3.11.6-200.fc19.x86_64 type: libreport Potential duplicate: bug 957341
de01770e6cbc86f19a13daa5b9fbba24b5f5838f adds a dontaudit for this in git.
back ported.
selinux-policy-3.12.1-74.12.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/selinux-policy-3.12.1-74.12.fc19
Package selinux-policy-3.12.1-74.12.fc19: * should fix your issue, * was pushed to the Fedora 19 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing selinux-policy-3.12.1-74.12.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-20980/selinux-policy-3.12.1-74.12.fc19 then log in and leave karma (feedback).
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 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 this bug is closed as described in the policy above. 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 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.