Date: Sun, 05 Oct 2008 07:34:09 -0500 From: eculp <eculp@encontacto.net> To: freebsd-current@freebsd.org Subject: Re: SSH Brute Force attempts Message-ID: <20081005073409.62441itn43jvde80@econet.encontacto.net> In-Reply-To: <4046.82.41.242.250.1223173482.squirrel@mail.elegosoft.com> References: <48E16E93.3090601@gmail.com> <48E4368E.4020404@gmail.com> <4046.82.41.242.250.1223173482.squirrel@mail.elegosoft.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Quoting sk@elegosoft.com: > mornin' > > Rich Healey wrote: >>> Recently I'm getting a lot of brute force attempts on my server, in the >>> past I've used various tips and tricks with linux boxes but many of them >>> were fairly linux specific. > > > disable pasword authentication OR use very strong passwords (24 chars) > OR use OTP > > if it is applicable you could limit access by hosts (from=3D) > > nothing of the above is linux or BSD specific > > btw. Software to delay Login Attempts could be tricked. > >> Personally I find that changing the port to anything other than 22 stops >> a lot of the skiddie brute force attacks. Thats not to say you >> shouldn't use something else as well - but it is something. > > it works for one of my servers too, but is security by obscurity It worked for me also but in addition I have started accepting ssh =20 from only known ip's but I always have a server with a known ip that =20 uses an alternative port for ssh that I can access from, lets say an =20 internet cafe or like, and then triangle to the server that I'm really =20 interested in. Hope that makes some sense. ed > > regards > Stefan > > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20081005073409.62441itn43jvde80>