public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Nikos Chantziaras <realnc@arcor.de>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user]  Re: Why isn't sshd blocking repeated failed login    attempts?
Date: Wed, 21 Jan 2009 14:36:39 +0200	[thread overview]
Message-ID: <gl74sk$8ov$1@ger.gmane.org> (raw)
In-Reply-To: <58965d8a0901201354n30001077v3771d17ec20b4b03@mail.gmail.com>

Paul Hartman wrote:
> I'm using the online denyhosts synchronization database, I think that
> may negatively affect how often it blocks hosts locally, because it
> waits until it does a remote sync to scan the local file. This is my
> theory. I like the idea of sharing my blocks and taking advantage of
> the blocks of others, but if it renders the program ineffective
> against the IP /actively/ attacking my system, then it's pointless.
> 
> I'm going to turn off the online sharing of denyhosts and see if it
> makes a difference.
> 
> Otherwise I guess I need to set up some kind of local firewall on this
> machine to get any more fine control over the connections.

The shared list of attackers doesn't have anything to do with it. 
Denyhosts checks the logs every X seconds.  I think 30 by default, not 
sure.  In that time, there can be many more attempted logins then the 
maximum you have configured in Denyhosts.

Also, the downloaded list of known attack hosts is copied locally into 
your hosts.deny file.  That's all there is to it.




  reply	other threads:[~2009-01-21 12:37 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     ` Nikos Chantziaras [this message]
2009-01-21 14:35       ` [gentoo-user] " 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
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='gl74sk$8ov$1@ger.gmane.org' \
    --to=realnc@arcor.de \
    --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