Breakin attempt

Polytropon freebsd at
Sat Oct 22 14:51:21 UTC 2011

On Sat, 22 Oct 2011 15:37:55 +0100, Bruce Cran wrote:
> On 22 Oct 2011, at 15:12, Polytropon wrote:
> > 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?
> If you run some sort of shell server, or where many people
> need to login using ssh, you'll have a bit of a support
> problem telling people to select the non-default port.

No problem here, as login systems are preconfigured and
come with "hardcoded" settings. No "user-serviceable"
parts inside. :-)

> Also, some might consider it security through obscurity,
> which is often said to be a bad thing.

Okay, that's a pragmatic reason I do understand.

But: There are no basic _technical_ reasons NOT to move the
SSH system to a nonstandard port, right?

I'm aware that a portscan might reveal the "hidden" SSH port,
but this solution at least terminates the break-in activity
on the default port (which seems to be the main target in
most cases).

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

More information about the freebsd-questions mailing list