From: Paul Hartman <paul.hartman+gentoo@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Why isn't sshd blocking repeated failed login attempts?
Date: Thu, 22 Jan 2009 10:46:43 -0600 [thread overview]
Message-ID: <58965d8a0901220846j13c888b1lca08df02a87fd6d4@mail.gmail.com> (raw)
In-Reply-To: <061701c97caf$c5e21960$6400a8c0@quan>
On Thu, Jan 22, 2009 at 10:37 AM, James Homuth <james@the-jdh.com> wrote:
>
>
> -----Original Message-----
> From: news [mailto:news@ger.gmane.org] On Behalf Of Nikos Chantziaras
> Sent: January 22, 2009 11:07 AM
> To: gentoo-user@lists.gentoo.org
> Subject: [gentoo-user] Re: Why isn't sshd blocking repeated failed login
> attempts?
>
> Paul Hartman wrote:
>> On Wed, Jan 21, 2009 at 11:53 AM, Nikos Chantziaras <realnc@arcor.de>
> wrote:
>>> Can you check the logs to see the timespan in which those hundreds of
>>> attempts took place? Also, what's the time interval Denyhosts checks
>>> for login attempts?
>>
>> The most recently denied host from this afternoon made over 200 login
>> attempts in a span of 17 minutes before denyhosts caught it. In my
>> denyhosts.conf I have these:
>>
>> DENY_THRESHOLD_INVALID = 3
>> DENY_THRESHOLD_VALID = 3
>> DENY_THRESHOLD_ROOT = 1
>> DENY_THRESHOLD_RESTRICTED = 1
>
> What is the value of DAEMON_SLEEP?
>
>
> Denyhosts doesn't pick up on certain types of PAM auth regular expressions.
> If any of those appear in your logs during those 200+ attempts, Denyhosts is
> probably not reading them. I've already reported it
> (http://bugs.gentoo.org/show_bug.cgi?id=248047) if you want to add anything
> to it.
I don't use PAM in sshd so I don't think that's my problem, but the
whole regexp thing is a possiblity in general as someone else
suggested. I will check into it tonight after work.
Thanks,
Paul
next prev parent reply other threads:[~2009-01-22 16:46 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-20 21:33 [gentoo-user] Why isn't sshd blocking repeated failed login attempts? Paul Hartman
2009-01-20 21:47 ` Etaoin Shrdlu
2009-01-22 13:40 ` Guillermo Garron
2009-01-20 21:49 ` Joshua Murphy
2009-01-20 21:54 ` Paul Hartman
2009-01-21 12:36 ` [gentoo-user] " Nikos Chantziaras
2009-01-21 14:35 ` Paul Hartman
2009-01-21 14:56 ` Neil Bothwick
2009-01-21 17:53 ` Nikos Chantziaras
2009-01-21 22:49 ` Paul Hartman
2009-01-22 8:31 ` Mick
2009-01-22 12:06 ` Robin Atwood
2009-01-22 16:06 ` Nikos Chantziaras
2009-01-22 16:18 ` Paul Hartman
2009-01-22 16:37 ` James Homuth
2009-01-22 16:46 ` Paul Hartman [this message]
2009-01-23 18:26 ` Mick
2009-01-23 20:22 ` Paul Hartman
2009-01-23 21:18 ` Paul Hartman
2009-01-23 21:34 ` Paul Hartman
2009-01-26 20:10 ` Paul Hartman
-- strict thread matches above, loose matches on Subject: below --
2009-01-23 20:33 Alan McKinnon
2009-01-23 20:54 ` Paul Hartman
2009-01-23 21:00 ` Alan McKinnon
2009-01-24 15:09 ` Steven Lembark
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=58965d8a0901220846j13c888b1lca08df02a87fd6d4@mail.gmail.com \
--to=paul.hartman+gentoo@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox