Strange, because the DEBUG entries shows that he was blocked pretty
quickly. Maybe you didn't restart DH after you initially changed the
config?
Phil
On Tue, 6 May 2008, René Berber wrote:
Phil Schwartz wrote:
That particular output indicates the your changed regex is being
recognized
Phil Schwartz wrote:
Strange, because the DEBUG entries shows that he was blocked pretty
quickly. Maybe you didn't restart DH after you initially changed the
config?
No, that's not the problem. If you mean restart after I added my
REGEX7, then DH has been restarted many times after that,
When you restart DH what does it show in the denyhosts.log as your
FAILED_ENTRY_REGEX7? eg:
tail -100l /var/log/denyhosts | grep FAILED_ENTRY_REGEX7
Regards,
Phil
On Tue, 6 May 2008, René Berber wrote:
Hi,
Here's a fragment of log that shows unexpected DH behaviour:
May 6 15:34:45
Phil Schwartz wrote:
When you restart DH what does it show in the denyhosts.log as your
FAILED_ENTRY_REGEX7? eg:
tail -100l /var/log/denyhosts | grep FAILED_ENTRY_REGEX7
2008-05-06 16:32:28,666 - prefs : INFOFAILED_ENTRY_REGEX7:
[User (?Puser\S+) from (?Phost\S+) not
