Changing SSH Port
Discussions center on whether moving SSH from the default port 22 reduces automated brute-force attacks, log noise, and low-effort bots, with consensus that it helps despite not providing real security against targeted threats.
Activity Over Time
Top Contributors
Keywords
Sample Comments
From experience, running ssh on non-default port have mostly reduced automated login attempts to 0, year after year.
While it doesn't give any real security, changing the ssh port will at least filter out these kinds of attacks.
You're making no sense. Moving the SSH port is a trivial way to reduce your attack surface (undirected bulk scans go for 22).
Change the default ssh port. Most of the attacks are from automated crawlers that try to brute force port 22. Your logs will become much more manageable.
I set my SSH port to something with a high number that is not used by any other known service. Drive-by attacks dropped to 0.
Is changing SSH port really necessary? If your SSH is vulnerable, attackers will find the Port for it.
Moving SSH to a different port does nothing if your system is being specifically targeted, but it stops 99% of drive-by bots. Not that they do much anyway but it at least stops them from showing up in your logs.
Also...stick the SSH on a non-default port. Cuts login attempts down to near zero.
Just changing my SSH port to 900 has reduced the amount of brute force by a fraction.
I always change the ssh port to something other than 22. It has always seemed to work well for me for most automated attacks. Perhaps this is not advisable for some reason?