Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 19 Sep 2006 17:25:43 -0400
From:      Nicolas Blais <nb_root@videotron.ca>
To:        freebsd-questions@freebsd.org
Cc:        "Dan Mahoney, System Admin" <danm@prime.gushi.org>
Subject:   Re: sshd brute force attempts?
Message-ID:  <200609191725.43937.nb_root@videotron.ca>
In-Reply-To: <70e8236f0609191412p5779d94cqa16df5631f4de916@mail.gmail.com>
References:  <20060919165400.A4380@prime.gushi.org> <70e8236f0609191412p5779d94cqa16df5631f4de916@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Tuesday 19 September 2006 17:12, Joao Barros wrote:
> On 9/19/06, Dan Mahoney, System Admin <danm@prime.gushi.org> wrote:
> > Hey all,
> >
> > I've looked around and found several linux-centric things designed to
> > block brute-force SSH attempts.  Anyone out there know of something a bit
> > more BSD savvy?
> >
> > My best attempt will be to get this:
> >
> > http://www.csc.liv.ac.uk/~greg/sshdfilter/index_15.html
> >
> > running and adapt it.
> >
> > I've found a few things based on openBSD's pf, but that doesn't seem to
> > be the default in BSD either.
> >
> > Any response appreciated.
>
> I'm using BruteForceBlocker quite successfully.
> I take the opportunity to thank danger for it :-)
>
> http://www.freshports.org/security/bruteforceblocker/

I like to protect myself by hiding what I have, which will reduce the amount 
of direct or random attacks by a lot, then deal with attacks using tools 
(like bruteforceblocker). 

This is especially useful when attackers are using ip-range tools to scan 
common ports for their associated service.

Why keep sshd on port 22?

Nicolas

-- 
FreeBSD 7.0-CURRENT #0: Sun Sep 17 10:21:02 EDT 2006     
nicblais@clk01a:/usr/obj/usr/src/sys/CLK01A 
PGP? : http://www.clkroot.net/security/nb_root.asc



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200609191725.43937.nb_root>