Package: fail2ban
Version: 0.8.6-3
Followup-For: Bug #620760
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Dear Maintainer,
The issue (looking in /var/log/dropbear instead of /var/log/auth.log) still
exists in this version of fail2ban. In addition, the
issues with the regexps are
Yaroslav Halchenko wrote:
anyways -- have you considered submitting the patch logging *all* failed
IPs against Debian's package of dropbear? may be it could be accepted.
Feel free to provide an argument that it would allow to use fail2ban and
make Debian users more secure.
why your patch
On Mon, 04 Apr 2011, Francis Russell wrote:
So, I sent the patch to the upstream author late December 2008. They
responded that logging IP's for failed logins seemed like a useful idea
and that they would commit that bit. Anyway, I watched the upstream repo
and the patch was never committed.
Package: fail2ban
Version: 0.8.4+svn20110323-1
Severity: normal
So I when upgrading noticed that a conf file I wrote ages ago has been
incorporated into fail2ban. However, the config section in jail.conf is
rather broken.
The default behaviour of the dropbear package is to install an init
Hi Francis,
thank you for your feedback, sorry for mixing up a jail definition a bit
;) I guess I will fix it up with the next upload
anyways -- have you considered submitting the patch logging *all* failed
IPs against Debian's package of dropbear? may be it could be accepted.
Feel free to
5 matches
Mail list logo
