public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Justin <justin@j-schmitz.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] SSH brute force attacks and blacklist.py
Date: Wed, 27 Feb 2008 20:07:37 +0100	[thread overview]
Message-ID: <47C5B4F9.9060701@j-schmitz.net> (raw)
In-Reply-To: <47C5A316.8010303@shic.co.uk>



Steve schrieb:
> I can't believe that I'm the only person with this, so it's probably 
> worth asking.
>
> I'm one of the (many) people who has opportunists trying usernames and 
> passwords against SSH... while every effort has been made to secure 
> this service by configuration; strong passwords; no root login 
> remotely etc.  I would still prefer to block sites using obvious 
> dictionary attacks against me.
>
> I used to use DenyHosts - but that became annoying as it used rather a 
> lot of resources (and relied upon tcp wrappers... which, I'm informed 
> are somewhat old-fashioned)
>
> I migrated to try using iptables as my firewall and using blacklist.py 
> - which I got working after some minor config-tweaking.  I'm aware 
> that there is configuration in the blacklist.py script for 
> BLOCKING_PERIOD - but what I really miss the "blocked forever" nature 
> of the DenyHosts alternative.... though I prefer every other aspect of 
> the iptables/blacklist.py approach.
>
> Has anyone else resolved this?  As far as I'm concerned, once I detect 
> someone has attempted a brute force (which blaclist.py does 
> fantastically well) what I want is for no further communication to be 
> accepted from the IP address - even after I reboot etc.  While I don't 
> know which sites I want to be accessible from in advance, I can be 
> sure none of them would launch a brute force attack against me. :-)
>
> Recommendations?
>
> I'm looking for the neatest Gentoo way to do this... rather than 
> recommendations for how to write something to do what I want from 
> scratch...
>
> Steve
>

Try fail2ban. I started as newby on iptables and I still am, because it 
is very easy to configure and does it job perfect.

http://gentoo-wiki.com/HOWTO_fail2ban
http://www.fail2ban.org/wiki/index.php/Main_Page
-- 
gentoo-user@lists.gentoo.org mailing list



  parent reply	other threads:[~2008-02-27 19:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-27 17:51 [gentoo-user] SSH brute force attacks and blacklist.py Steve
2008-02-27 18:09 ` [gentoo-user] " 7v5w7go9ub0o
2008-02-27 18:14   ` 7v5w7go9ub0o
2008-02-27 18:12 ` [gentoo-user] " Alan McKinnon
2008-02-27 19:07 ` Justin [this message]
2008-02-27 21:39   ` [gentoo-user] " Anno v. Heimburg
2008-02-28 16:31     ` Willie Wong
2008-02-27 20:24 ` Remy Blank
2008-02-27 23:01   ` Iain Buchanan
2008-02-28  9:55   ` Etaoin Shrdlu
2008-02-28 11:13     ` Steve
2008-02-28 16:19       ` Willie Wong

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=47C5B4F9.9060701@j-schmitz.net \
    --to=justin@j-schmitz.net \
    --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