> I'm probably not aware of all the implications of different
> misconfigurations, but I thought 329163 was about the problems that
> happen if, for example, fail2ban-ssh is missing. In contrast, in the
> case I'm thinking of, fail2ban-ssh (the table) is present, but there
> are no references to i
On Tue, Oct 04, 2005 at 03:18:27PM -0400, Yaroslav Halchenko wrote:
> On Tue, Oct 04, 2005 at 11:29:45AM -0700, Ross Boylan wrote:
> > concerns the program operation and endless loop. This one concerns
> > primarily user information (which may have been addressed) and the
> > problem that the fire
On Tue, Oct 04, 2005 at 11:29:45AM -0700, Ross Boylan wrote:
> concerns the program operation and endless loop. This one concerns
> primarily user information (which may have been addressed) and the
> problem that the firewall rules become ineffective if the main INPUT
> chain is altered so at to
On Tue, Oct 04, 2005 at 02:17:29PM -0400, Yaroslav Halchenko wrote:
> Would you mind me merging this bug with
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=329163
> ?
> they seems to be about the same problem
> or I misinterpreted it?
It's in the same neighborhood, but a different building.
Would you mind me merging this bug with
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=329163
?
they seems to be about the same problem
or I misinterpreted it?
and btw note about it is included in README.Debian since 0.5.2-5 :-)
--
.-.
=---
Package: fail2ban
Version: 0.5.2-4
Severity: wishlist
It would be good to note that if the user has or modifies the INPUT
chain they will need to include rules (and their names) to keep
fail2ban working.
I didn't appreciate this and accidentally disabled it.
Also, I'm not sure if the rules will
6 matches
Mail list logo
