3 ms·
This will be great. We can finally deprecate sudo on systemd systems. Then we should be able to deprecate PAM, setuid bit, etc.
by immibis 3y ago
This will be great. We can finally deprecate sudo on systemd systems. Then we should be able to deprecate PAM, setuid bit, etc.
- yjftsjthsd-h 3y agoI can see creating a system with zero setuid files, but I don't think this reduces PAM use, does it?
- eichin 3y agoNot setuid generically, but `sudo` itself has a bunch of pam support/dependency.
- yjftsjthsd-h 3y agoI would expect sudo to also touch pam a lot, but AIUI systemd also uses pam through polkit for its ~native permission system - https://serverfault.com/questions/841306/authentication-is-required-to-manage-system-services-or-units https://serverfault.com/questions/841306/authentication-is-r...
- cedws 3y agoI wonder, are there any distros already with a nosuid root?
- Retr0id 3y agoIs removing setuid actually a win? I know it presents a security risk, but it feels like we're not actually removing that attack surface, just moving it around.
- NekkoDroid 3y agoWell... that "attack surface" isn't new, its mostly just repackaging systemd-run, which is just used to tell PID1 to launch a new process. So in total the attack surface would be reduced by removing sudo.