Earlier quoted context omitted.
My only thought is even with password auth. turned off hostile persons can still connect to the ssh daemon and might discover and unknown vulnerability or some type of dos. If you know someone is trouble why let them in even if you are wearing armor?
It'd really suck if they could forge traffic from you that looked like a failed login attempt and that resulted in you getting banned.
How I spend my first 5 minutes on a server
31–40 of 355 posts
Re: How I spend my first 5 minutes on a server
#32I've never understood the point of fail2ban if you disable ssh password authentication. Yeah, it might eliminate some spam in the logs, but if you only allow key-based authentication that doesn't really matter.
Re: How I spend my first 5 minutes on a server
#33I also recommend changing the default SSH port.
Re: How I spend my first 5 minutes on a server
#34Re: How I spend my first 5 minutes on a server
#35The chances of both that and the deploy user getting corrupted at the same time is unlikely.
Re: How I spend my first 5 minutes on a server
#36Also a big fan of externally verifying what ports are open, and making sure the system is in monitoring, backup, config management systems. Config management is kind of optional if you have a small number of servers which don't duplicate configurations, though, and there's often no need to back up the OS, but any data should be backed up automatically.
Re: How I spend my first 5 minutes on a server
#37Re: How I spend my first 5 minutes on a server
#38The first five minutes on any of my servers involve giving it a name, installing puppet and adding the server name to my central puppet config. You seriously do this by hand for every server? That seems error prone and a huge waste of time when tools like puppet and chef exist.
Puppet and Chef are yet another thing to learn and maintain, if the guy is a part-time admin with a lot of other responsibilities and a small number of servers it may not be worth it.