3 ms·
Lots of reasons… Tracking actions, fine grained policy controls, sharing a root password amongst multiple people, and then there is the risk of accidentally ru
by edf13 4y ago
Lots of reasons…
Tracking actions, fine grained policy controls, sharing a root password amongst multiple people, and then there is the risk of accidentally running a cmd as root when you thought you were in your home shell!
- dx034 4y agoConfusing the server I'm on will always cause issues, not matter if I have to sudo for root. I get the other points, but most servers I encountered don't have these fine grained controls because doing manual work on them only happens for debugging or fixing issues. And the password doesn't need to be shared with sth like Tailscale. Tracking actions is a good part though, I wonder if you can still track which tailscale user was responsible for that root login.