+++ This bug was initially created as a clone of Bug #244275 +++
Description of problem (copied from Bug #244275):
fail2ban doesn't require shorewall to function, and in fact, as we ship it, it
makes use of the Fedora firewall - installing an extra firewall which is the not
used in the default configuration is a bit gratuitous and confusing to the user.
Also, the Requires: tcpwrappers isn't needed unless the user decides to enable
the tcpwrapper action (disabled by default)
Bug #244275 contains suggestions and possible patches for a fix, but was closed with NOTABUG as noted in the comment from the EPEL maintainer:
--- Additional comment from email@example.com on 2012-01-12 22:46:49 EST ---
Since this is just the EPEL package and I don't maintain fail2ban for Fedora, I will be keeping it in line with Fedora proper. Please feel free to discuss this with the Fedora package maintainer.
As I wrote in some comments in Bug #244275, I'm interested in a fix for Fedora,
which is why I file this bug now.
fail2ban-0.8.8-3.fc18 has been submitted as an update for Fedora 18.
fail2ban-0.8.8-3.fc17 has been submitted as an update for Fedora 17.
* should fix your issue,
* was pushed to the Fedora 18 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.8-3.fc18'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
fail2ban-0.8.8-3.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.
fail2ban-0.8.8-3.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.