On Mon, May 23, 2011 at 01:51:59PM +0200, Jérôme Warnier wrote: > There does not seem to be any development ongoing at all. It seems dead > upstream. > I'm considering moving to a more powerful alternative (fail2ban).
I have spoken with Phil Schwartz, the upstream maintainer, in attempt to introduce some more transparency and agility in the development process. It appears that the next release of denyhosts has been held up by a few technical issues which I am hoping to help resolve. While I would not blame you for using fail2ban, I did want to inform you that denyhosts should be seeing some activity in the near future. As for this particular bug, the current issue is simply that Dropbear does not use TCP Wrapper as OpenSSH does. This means that denyhost's current method of using /etc/hosts.deny would not work for Dropbear. I believe this is enough reason to tag this bug wontfix, but because it is an upstream bug, I will let Phil make the final call. Thanks - Kyle Willmon -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
