Date: Sat, 22 Oct 2011 13:11:27 -0400 From: Lowell Gilbert <freebsd-questions-local@be-well.ilk.org> To: Polytropon <freebsd@edvax.de> Cc: freebsd-questions@freebsd.org Subject: Re: Breakin attempt Message-ID: <444nz17xz4.fsf@lowell-desk.lan> In-Reply-To: <20111022161242.11803f76.freebsd@edvax.de> (Polytropon's message of "Sat, 22 Oct 2011 16:12:42 %2B0200") References: <000001cc90c0$a0c16050$e24420f0$@org> <4EA2CE72.5030202@cran.org.uk> <20111022161242.11803f76.freebsd@edvax.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Polytropon <freebsd@edvax.de> writes: > On Sat, 22 Oct 2011 15:08:50 +0100, Bruce Cran wrote: >> I suspect that these sorts of attacks are fairly normal if you're >> running ssh on the standard port. I used to have lots of 'break-in >> attempts' before I moved the ssh server to a different port. > > Is there _any_ reason why moving from port 22 to something > different is _not_ a solution? > > Reason why I'm asking: Moving SSH away from its default port > seems to be a relatively good solution as break-in attempts > concentrate on default ports. So in case a sysadmin decides > to move SSH to a "hidden" location, what could be an argument > against this decision? Connecting from behind other people's paranoid firewalls gets difficult on other ports.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?444nz17xz4.fsf>