Re:Moving your SSH port isn’t security by obscurity
by crawlcrawler on Monday September 21, 2020 @06:02PM
(#24548950)
I love Brian Regan but I have to say, even though I'm probably ruining one of his best jokes [0], that the plural form of "box" is not "boxen".
[0] https://www.youtube.com/watch?v=xkrMsPiqG6M&feature=youtu.be...
Re:Moving your SSH port isn’t security by obscurity
by edoceo on Monday September 21, 2020 @06:08PM
(#24548989)
Oh, I'm aware it's "boxes". But, I got into the "boxen" habit in the middle 90s and now that I'm "old" I've chosen to become stubborn and stuck in my ways. Also, I think it's more fun. I've got other things to be pedantic about.
Re:Moving your SSH port isn’t security by obscurity
by dllthomas on Monday September 21, 2020 @06:23PM
(#24549099)
I'm pretty sure "Unix boxen" predates Brian Regan's standup.
Re:Moving your SSH port isn’t security by obscurity
by zimpenfish on Monday September 21, 2020 @07:17PM
(#24549418)
OpenSSH on port 22 gets at least one attempt a minute for me (and that's with fail2ban blocking IPs on a single failure.) Dropbear on port 2222 gets at most one an hour.
Re:Moving your SSH port isn’t security by obscurity
by zimpenfish on Tuesday September 22, 2020 @03:20AM
(#24551835)
Since I cleaned out and restarted fail2ban yesterday (~1800BST), the sshd:22 filter has banned 291 IPs whilst the dropbear:2222 filter has banned 8.
On the other 20+ boxen with ssh on port xxx22 the logs and f2b rules are much smaller - which means less hassle for the admin.
And on the boxen with services behind WG there is zero noise.
Naturally we're using keys only with all this. The reduced noise in the logs/rules/firewall are very handy.