Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 22 Oct 2011 17:10:44 +0200
From:      "Hasse Hansson" <>
To:        "'Polytropon'" <>, "'Bruce Cran'" <>, "'Michael Powell'" <>
Subject:   SV: Breakin attempt
Message-ID:  <000f01cc90cc$c8c0abe0$5a4203a0$@org>
In-Reply-To: <>
References:  <000001cc90c0$a0c16050$e24420f0$@org>	<> <>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help

-----Oprindelig meddelelse-----
[] P=E5 vegne af Polytropon
Sendt: den 22 oktober 2011 16:13
Til: Bruce Cran
Emne: Re: Breakin attempt

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=20
> running ssh on the standard port. I used to have lots of 'break-in=20
> 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?

Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...

Thank you all Polytropon, Matthias, Bruce and Michael for your answers.
No, no reason at all to not change from port 22, and I will follow that
And my plan is to move away from password based ssh logins in the =
I've been running this server for educational purposes for several =
But this is first time I've had a "Break in attempt" going on for this =

It don't bother me more than cluttering up my logfiles, but I got =
curious if
Attempt was originating from one person.

All the Best to you all

_______________________________________________ mailing list
To unsubscribe, send any mail to =

Want to link to this message? Use this URL: <$c8c0abe0$5a4203a0$>