Date: Thu, 23 Sep 2004 06:52:29 +0200 From: Nick Cleaton <nick@cleaton.net> To: freebsd-security@freebsd.org Subject: Re: Attacks on ssh port Message-ID: <20040923045229.GJ5340@lt1.cleaton.net> In-Reply-To: <20040918222819.GG20449@pir.net> References: <414C2798.7060509@withagen.nl> <6917b781040918103077c76f0c@mail.gmail.com> <414CAC56.8020601@withagen.nl> <6917b781040918150446b7dada@mail.gmail.com> <414CB5EF.7080901@withagen.nl> <20040918222819.GG20449@pir.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Sep 18, 2004 at 06:28:19PM -0400, Peter Radcliffe wrote: > > Personally I only allow ssh from known legitimate sources and block the > rest so the "noise" is in a completely different list. > I want access to my system from any IP address, so I've patched my sshd so that a secret token is required to connect. Kinda like using an obscure port, only more so :) http://nick.cleaton.net/openssh-3.8p1-cc-0.03.patch Nick -- $_='YN8KuE*** http://www.exonetric.com/ Telehouse UK colo ***HARQr**' .'NfzV0YrC1*** GBP40/month +VAT 40G BW no setup fee ***MnjJ**' .'6QvtcPgQ20*** ***nlS**' ;s/(.)(.*(.))/$2.chr(32+(ord($1)+ord$3)%89)/euntil/Foo/;eval#****'
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040923045229.GJ5340>