this post was submitted on 19 Nov 2026
51 points (91.8% liked)

Linux

15533 readers
296 users here now

A community for everything relating to the GNU/Linux operating system (except the memes!)

Also, check out:

Original icon base courtesy of lewing@isc.tamu.edu and The GIMP

founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] lntl@lemmy.sdf.org 8 points 2 days ago (2 children)

I would add changing the SSH port to one that isn't 22. This isn't any more secure, but does tamp down on automated scanner traffic.

[–] exdor@programming.dev 6 points 1 day ago (1 children)

You can also add endlesssh behind port 22 to slow down attackers, and of course install fail2ban

[–] lntl@lemmy.sdf.org 2 points 1 day ago

Thanks for sharing, never heard of endlesssh and tonight ima gonna reopen port 22 :)

[–] shalafi@lemmy.world -1 points 1 day ago (1 children)

Isn't adding a key more than enough?

[–] lntl@lemmy.sdf.org 3 points 1 day ago (1 children)

keys are more than enough for security but keya doesn't reduce automated scanner traffic at all. for each automated scan, the server will open a connection and attempt to authenticate the client which consumes resources and spams logs. When I switched to a different port, my automated scanner traffic dropped to essentially zero.

[–] shalafi@lemmy.world 3 points 22 hours ago

Gotcha! Yeah, I never left default ports at my last job and my only remaining personal server is on 22, but it's under zero load.