On Mon, 15 Jul 2013, Steven Hiscocks wrote:
>    In server/filter.py:
>  > @@ -371,6 +371,9 @@ def findFailure(self, timeLine, logLine):
>  >                            else:
>  >                                    try:
>  >                                            host = failRegex.getHost()
>  > +                                          if returnRawHost:
>  > +                                                  failList.append([host, date])
>  > +                                                  break

>    This should now be checked in changes with [1]#298, as part of samples
>    test cases.
>    Was your suggestion that this should also be flagged up when actually
>    running fail2ban?

yeap... if we see it while running our tests or new configs, we would
know that our configuration has redundant regexes.

If user runs it (possibly after adding few "custom" regexes) --
those warning could be a sign that his regexes are not only redundant
but could well be too loose.

in any case -- some attention better be paid to those.

-- 
Yaroslav O. Halchenko, Ph.D.
http://neuro.debian.net http://www.pymvpa.org http://www.fail2ban.org
Senior Research Associate,     Psychological and Brain Sciences Dept.
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1 (603) 646-9834                       Fax: +1 (603) 646-1419
WWW:   http://www.linkedin.com/in/yarik