sudo-rs doesn’t implement all the functionality of regular sudo, which causes certain applications to break. I had to install sudo.ws on the latest Ubuntu to get regular sudo back. Many installation scripts depend on sudo, not alternatives.
It’s simple to just symlink whatever you want to sudo and have it work in the same way. These alternatives implement enough for most use cases to make them viable IMO.
Any software that invokes a privilege escalation utility should have a setting or option to choose which such utility should be invoked. Otherwise the software should be run with already escalated privileges, if it needs them to function. Or call a library that can do privilege escalation, after asking for credentials.
Not really. With sudo you can to set the correct selinux contexts when running commands (on selinux enabled systems). Doas and sudo-rs don’t seem to support this currently.
Nah we got several alternatives, like sudo-rs, doas (my personal choice), please, etc. All good.
sudo-rs doesn’t implement all the functionality of regular sudo, which causes certain applications to break. I had to install sudo.ws on the latest Ubuntu to get regular sudo back. Many installation scripts depend on sudo, not alternatives.
It’s simple to just symlink whatever you want to sudo and have it work in the same way. These alternatives implement enough for most use cases to make them viable IMO.
Any software that invokes a privilege escalation utility should have a setting or option to choose which such utility should be invoked. Otherwise the software should be run with already escalated privileges, if it needs them to function. Or call a library that can do privilege escalation, after asking for credentials.
That’s my take. 🤷♂️
Not really. With sudo you can to set the correct selinux contexts when running commands (on selinux enabled systems). Doas and sudo-rs don’t seem to support this currently.
Not really what? What are you referring to?
That a simple symlink of sudo to a replacement will suffice.