Description of problem: The update for fail2ban that was pushed in the last few days has introduced a new AVC when log rotation runs: time->Mon May 26 03:17:18 2014 type=SYSCALL msg=audit(1401070638.486:461440): arch=40000003 syscall=11 success=no exit=-13 a0=931e6c0 a1=931e700 a2=931daa0 a3=931e700 items=0 ppid=8568 pid=8569 auid=0 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 ses=3975 tty=(none) comm="sh" exe="/usr/bin/bash" subj=system_u:system_r:logrotate_t:s0-s0:c0.c1023 key=(null) type=AVC msg=audit(1401070638.486:461440): avc: denied { execute } for pid=8569 comm="sh" name="fail2ban-client" dev="sda1" ino=76045 scontext=system_u:system_r:logrotate_t:s0-s0:c0.c1023 tcontext=system_u:object_r:fail2ban_client_exec_t:s0 tclass=file ---- time->Mon May 26 03:17:18 2014 type=SYSCALL msg=audit(1401070638.487:461441): arch=40000003 syscall=33 success=no exit=-13 a0=931e6c0 a1=1 a2=b7774000 a3=0 items=0 ppid=8568 pid=8569 auid=0 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 ses=3975 tty=(none) comm="sh" exe="/usr/bin/bash" subj=system_u:system_r:logrotate_t:s0-s0:c0.c1023 key=(null) type=AVC msg=audit(1401070638.487:461441): avc: denied { execute } for pid=8569 comm="sh" name="fail2ban-client" dev="sda1" ino=76045 scontext=system_u:system_r:logrotate_t:s0-s0:c0.c1023 tcontext=system_u:object_r:fail2ban_client_exec_t:s0 tclass=file ---- time->Mon May 26 03:17:18 2014 type=SYSCALL msg=audit(1401070638.487:461442): arch=40000003 syscall=33 success=no exit=-13 a0=931e6c0 a1=4 a2=b7774000 a3=0 items=0 ppid=8568 pid=8569 auid=0 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 ses=3975 tty=(none) comm="sh" exe="/usr/bin/bash" subj=system_u:system_r:logrotate_t:s0-s0:c0.c1023 key=(null) type=AVC msg=audit(1401070638.487:461442): avc: denied { read } for pid=8569 comm="sh" name="fail2ban-client" dev="sda1" ino=76045 scontext=system_u:system_r:logrotate_t:s0-s0:c0.c1023 tcontext=system_u:object_r:fail2ban_client_exec_t:s0 tclass=file Version-Release number of selected component (if applicable): selinux-policy-targeted-3.12.1-166.fc20.noarch
39b6bf616b5823c2ae883669b0749330235a26d2 fixes this in git, by allowing logrotate to execute all executables.
selinux-policy-3.12.1-167.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/selinux-policy-3.12.1-167.fc20
Package selinux-policy-3.12.1-167.fc20: * should fix your issue, * was pushed to the Fedora 20 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-167.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-7240/selinux-policy-3.12.1-167.fc20 then log in and leave karma (feedback).
selinux-policy-3.12.1-171.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/selinux-policy-3.12.1-171.fc20
Package selinux-policy-3.12.1-171.fc20: * should fix your issue, * was pushed to the Fedora 20 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-171.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-7499/selinux-policy-3.12.1-171.fc20 then log in and leave karma (feedback).
selinux-policy-3.12.1-171.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.