fail2ban insecurely uses predictable tmp files for the following actions: dshield mail-buffered sendmail-buffered mynetwatchman While mktemp in /tmp could work for some, others are are persistent (i.e. dshield), so need a predictable path like /var/lib/fail2ban. Note that SELinux currently allow fail2ban to work with files in /tmp. I'll create another bug with this blocking, as the solution for this should be decided before updating the policy. FYI, why predictable tmp files are : http://www.linuxsecurity.com/content/view/115462/151/
fail2ban-0.8.4-27.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/fail2ban-0.8.4-27.fc14
fail2ban-0.8.4-27.fc13 has been submitted as an update for Fedora 13. https://admin.fedoraproject.org/updates/fail2ban-0.8.4-27.fc13
fail2ban-0.8.4-27.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/fail2ban-0.8.4-27.fc15
Package fail2ban-0.8.4-27.fc15: * should fix your issue, * was pushed to the Fedora 15 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing fail2ban-0.8.4-27.fc15' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/fail2ban-0.8.4-27.fc15 then log in and leave karma (feedback).
fail2ban-0.8.4-27.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report.
fail2ban-0.8.4-27.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.
fail2ban-0.8.4-27.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.
*** Bug 700769 has been marked as a duplicate of this bug. ***
*** Bug 700763 has been marked as a duplicate of this bug. ***