There's consequences no matter what course of action you take. I
would say
generally SSH is a secure service (assuming you update your server
regularly)
but be aware:
a) SSH scans/probes are very common right now. Accounts with very
bad
passwords may get compromised by these worms. Moving to a non-
standard port
would circumvent this.
Not really. You just disguised the port but any smart attacker will
notice the service running on another port and switch to targeting
that.
FWIW, in our case, port 22 is swamped with "unsmart" attackers, to
the tune of 100s per minute, 24/7, making for logs too unwieldy to
even peruse. If we changed the port number, it would have the benefit
of reducing the noise level by 90%, and getting just the "smart"
attackers in the log.
I've tried a few "change port 22 how-tos", such as on MacOSX Hints,
but I've not found a procedure explained well enough that I could get
to work. (OSXS 10.4.9 PPC 2x2GHz G5)
