Re:Practical Linux Hardening Guide
by killaken2000 on Thursday January 24, 2019 @11:52PM
(#18995660)
Does it _harm_ security?
Perahaps not directly, but it does add to cognitive overhead and makes securing the system as a whole more difficult.
If your environment contains multiple ssh servers running on non-standard ports you would not notice when something out of the ordinary happens.
Something listening to an unexpected port should be something you must look into, not shrug at.
Re:Practical Linux Hardening Guide
by romeisendcoming on Monday January 28, 2019 @01:37PM
(#19019851)
So standardize on a non-standard port, document it and when you do have ssh probes assume it's targeted rather than just another l33t child running du-jour crack(x).
Moving to non-standard means more sophisticated discovery and possibly a more sophisticated attempt.
Re:Practical Linux Hardening Guide
by throwawaymath on Friday January 25, 2019 @12:34AM
(#18995825)
No, but it is non-standard. Why do things you don't need to?
Changing SSH to a non-standard port is an inelegant solution and doesn't actually bolster security.