It appears that this issue has already been fixed upstream, as can be seen
in the current source file for this filter at
https://github.com/fail2ban/fail2ban/blob/master/config/filter.d/named-refused.conf
Which has:
prefregex = ^%(__line_prefix)s(?: error:)?\s*client(?: @\S*)? #\S+(?:
The commit that fixes this is here:
https://github.com/fail2ban/fail2ban/commit/43954692260bc57f6b7afd08115f8906b8fabce0
As best I can tell, this issue seems to have been fixed in the 0.10.5
release.
Evan
On Thu, 4 Mar 2021, Evan Harris wrote:
It appears that this issue has already been
Hello,
Le 04/03/2021 à 14:39, E Harris a écrit :
Package: fail2ban
Version: 0.10.2-2.1
Severity: normal
There is a problem in the regex matching for the optional named-refused filter.
Log messages from named that should be matched by this filter are not being
matched because the log pattern
Package: fail2ban
Version: 0.10.2-2.1
Severity: normal
There is a problem in the regex matching for the optional named-refused filter.
Log messages from named that should be matched by this filter are not being
matched because the log pattern for the host is different than expected.
4 matches
Mail list logo
