> My style is to keep my old config file and then merge in the changes
> and restart after the main install is done.
whatever works for you is good with me :-)
> 1. The most substantive thing I notice is that the ignoreip
> configuration setting does not seem to be used--that is, I see no sign
> o
On Wed, Oct 12, 2005 at 11:24:53AM -0400, Yaroslav Halchenko wrote:
> Hi
>
> I've hacked a fix for the problem of "missing chain". Could you please
> try the most recent version (not yet in Debian mainstream) available
> from
>
> http://itanix.rutgers.edu/rumba/dists/unstable/perspect/binary-all/
Hi
I've hacked a fix for the problem of "missing chain". Could you please
try the most recent version (not yet in Debian mainstream) available
from
http://itanix.rutgers.edu/rumba/dists/unstable/perspect/binary-all/net/
While upgrading you might need to update your config file with a fresh
one s
Indeed such problem exists and there is a note in README.Debian:
Currently no checks if an iptables queue generated at the beginning
(fail2ban-http and fail2ban-ssh) exists. So if your firewall resets
the iptable rules -- it is your responsibility to restart fail2ban.
Upstream author decided to p
Package: fail2ban
Version: 0.5.3-1
Severity: normal
Fail2ban will go into an endless loop trying to ban an ip address,
if the chain it is expecting to find is no longer valid (for example if a user
restarts iptables).
On a busy system this has the potential to quickly fill up the log or mail
spo
5 matches
Mail list logo
