4 ms·

Show HN: Urdo, a "Replacement" for Sudo and Run0

2 points by gavinhoward 2y ago

After run0, systemd's replacement for sudo, was announced last week [0], I decided to write my own that doesn't require systemd. It's called urdo. Despite not touching sockets for 10 years, and then only once in University, I quickly got it done. I believe good programmers could do the same, and maybe more quickly. So you don't need systemd to replace sudo. [1] NOTE: "Replacement" is in quotes for a reason: YOU SHOULD NOT RUN THIS CODE! It's a proof-of-concept! This is also why I don't want to hear any complaints about the license. If you are more than just curious, though, contact me. [2] I'd be happy to keep working on urdo and provide license grants. [3] [0]: https://news.ycombinator.com/item?id=40205714 https://news.ycombinator.com/item?id=40205714 [1]: https://yzena.com/2024/05/you-do-not-need-systemd-to-replace-sudo/ https://yzena.com/2024/05/you-do-not-need-systemd-to-replace... [2]: https://yzena.com/contact/ https://yzena.com/contact/ [3]: https://yzena.com/services/#license-grants https://yzena.com/services/#license-grants

theamk 2y ago
I am not sure if this project is some sort of irony/sarcasm, or a real thing. In case it's latter: - "deprecated" does not mean "removed". For example, telnetd has been deprecated since 1999, and debian still provides "telnetd" package. I am sure that sudo will stick around for a few decades as well. - Even if sudo somehow disappears, there are plenty of replacements already. OpenBSD's "doas" is probably most well known, but there are other things, as well as DIY solutions like ssh'ing to localhost. - For the cases like that - highly security-critical software without any special requirements - one would want widely-used, well-tested software. And probably with a team behind it too, so the project does not go bad if sole author loses interest in it.
- gavinhoward 2y ago
  Author here. > - "deprecated" does not mean "removed". Right, but defaults matter. > - Even if sudo somehow disappears, there are plenty of replacements already. OpenBSD's "doas" is probably most well known I'm not talking about sudo, actually. I'm talking about suid, which if it is deprecated (not supported by distros; you can already turn it off), then doas won't work either. > but there are other things, as well as DIY solutions like ssh'ing to localhost. Yes, that is essentially what this does. > - For the cases like that - highly security-critical software without any special requirements - one would want widely-used, well-tested software. Yes, that is why I say not to use it. The whole point was to prove that you don't need systemd to get something working and that it could be relatively simple.

2 points by gavinhoward 2y ago

theamk 2y ago

I am not sure if this project is some sort of irony/sarcasm, or a real thing. In case it's latter: - "deprecated" does not mean "removed". For example, telnetd has been deprecated since 1999, and debian still provides "telnetd" package. I am sure that sudo will stick around for a few decades as well. - Even if sudo somehow disappears, there are plenty of replacements already. OpenBSD's "doas" is probably most well known, but there are other things, as well as DIY solutions like ssh'ing to localhost. - For the cases like that - highly security-critical software without any special requirements - one would want widely-used, well-tested software. And probably with a team behind it too, so the project does not go bad if sole author loses interest in it.

gavinhoward 2y ago
Author here. > - "deprecated" does not mean "removed". Right, but defaults matter. > - Even if sudo somehow disappears, there are plenty of replacements already. OpenBSD's "doas" is probably most well known I'm not talking about sudo, actually. I'm talking about suid, which if it is deprecated (not supported by distros; you can already turn it off), then doas won't work either. > but there are other things, as well as DIY solutions like ssh'ing to localhost. Yes, that is essentially what this does. > - For the cases like that - highly security-critical software without any special requirements - one would want widely-used, well-tested software. Yes, that is why I say not to use it. The whole point was to prove that you don't need systemd to get something working and that it could be relatively simple.