3 ms·
I think there are lots of perfectly valid reasons to use root logins over SSH. Sure, you absolutely shouldn't be doing development work or suchlike as root. Bu
by jcalvinowens 13y ago
I think there are lots of perfectly valid reasons to use root logins over SSH.
Sure, you absolutely shouldn't be doing development work or suchlike as root. But if you need to run administrative scripts on a bunch of servers, SSH as root is usually the easiest way to do that. I certainly trust sshd and RSA/ECDSA a lot more than some supposedly-secure setuid executable that lets me run commands as root.
Plus (as you probably know) you can specify in public key files that only certain IP addresses can log in using that keypair.
I've read that the general "don't log in as root" mentality is really an artifact of the telnet days when you didn't want people to sniff your passwords easily... not sure how true that is.
- jamiesonbecker 13y agoroot is prime target for brute force. not only that, but it's a violation of pci/fips/hippa/sox etc to share administrative accounts, so if you're a team of one that's one thing, but don't share root with anyone else.
- jcalvinowens 13y ago> root is prime target for brute force. So disable password logins. Even outside of root, that's a much more secure practice anyway.
- jamiesonbecker 13y agoalways disable password logins -- but that has nothing to do with disabling root login as well.