This sounds like a great improvement. I have read the sudo source code and anyone that seriously thinks there’s no problem with it being SUID is crazy.
That said the whole security model of sudo makes no sense. As soon as you can access a sudoers’ account you can trivially steal their password by MitMing sudo and waiting.
the whole security model of sudo makes no sense
I think that is a bit strong. Sure, you aren’t gaining much protection if you just allow sudo -su root but there are a lot of valid use cases.
- Logging.
- A bit of an “explicit” check to keep you from doing something stupid without thinking.
- You can configure sudo to only allow specific commands from different users. (Maybe a trusted friend should have permission to reboot your Minecraft server but nothing else)
They were so preoccupied wondering if they could, that they never stopped to ask if they should.
This way we will have multiple sudo-tools on one system without the ability to remove all but one. Like now with all this crap like systemd-resolved, systemd-networkd, systemd-anothershitd and a bunch of tools that do the same thing, but are all required.
Something worth reading regarding Systemd https://www.devuan.org/os/announce/ Cheers.
That doesn’t seem to clear up anything other than indicating that the fork was motivated by wanting to do things differently for the sake of being able to do things differently.
Which is fine, I do this often enough. But I don’t expect to get a lot of others to follow suit on that basis alone.
So went are we going to fully switch from GNU/Linux to SystemD/Linux?
