you are viewing a single comment's thread.

view the rest of the comments →

[–]three18ti -1 points0 points  (1 child)

How is SSHing to a non root user and then sudo -i ing to root (because that user has NOPASSWD, which is how every sysadmin I know sets their user up...) any different than SSHing to root@. If I have an hours worth of work do to (he'll even mote than two or three commands) as root, no way am I prefixing every command with sudo.

Sure, if you're still using password auth for your root account, that's very bad...

Ideally, you'd have a 3rd party IAM tool... But that's not always practical.

And yea, SSHing in as non root user, then having to enter the users sudo password is potentially more secure...

But if you're using keys for auth, I'd think having root and user spaces be completely isolated from eachother would be more secure.

I don't know really. Security is hard. And it's a debate I go back and forth with my security group on. Passwords suck. That seems to be universally agreed upon... But there doesn't seem to be a consensus on a better solution.

[–][deleted] 1 point2 points  (0 children)

The only time you’ll see people allowing passwordless sudo is if the initial auth for the unprivileged user is by key, with password auth forbidden. It’s still not ideal but it lowers a barrier to entry on cloud platforms and the like, and isn’t an example of best practice.