Earlier quoted context omitted.
The quoted paragraph has nothing to do with language choice.
They didn’t write in paragraphs, it is more like a collection of IRC posts or something. Here’s the whole post thingy: > God I wish they did. They wrote the program in C, (as far as I can tell) have no intention of rewriting it in Rust, and it's had many viable attacks over the years that allowed attackers to gain root privileges and worse. It's also debatable if the entire concept of privilege separation as implemen…
🥺: the best sudo replacement
101–110 of 559 posts
Re: 🥺: the best sudo replacement
#102Re: 🥺: the best sudo replacement
#103I mean clearly this is all quite tongue in cheek but: > It's also debatable if the entire concept of privilege separation as implemented in Linux and UNIX was a bad idea to begin with but we're stuck with it because of an endless ball of legacy programs controlled by egotistical open source people that refuse to change […] Not a very charitable way to describe volunteers who don’t want to learn the flavor-of-the-mont…
Rust? Well, speaking of egotistical open source people that refuse to change...
Re: 🥺: the best sudo replacement
#104> They wrote the program in C They wrote it in 1980 for unix; what exactly would you like them to have used? > (as far as I can tell) have no intention of rewriting it in Rust Since it will be less than a paragraph before you start ranting about how "obscure targets that nobody uses won't be able to leech off of the rest of the ecosystem by holding back any chance to let us have a modicum of nice things", I trust you…
I did write an actual replacement. It's what TFA is about :)
That is obviously not a replacement; either we take the serious approach of "sudo allows only authorized users to run things as root" and yours doesn't control access, or we take the nonserious approach of "sudo has so many bugs that it just gives people access" in which case we hardly need to bother rewriting it.
Re: 🥺: the best sudo replacement
#105Earlier quoted context omitted.
A appreciate you 'describing' the emoji for me. I'm on the spectrum, and I can't tell 99% of these things apart. Looks like a sad face to me. no different then the 500 other sad face emoji's I find. I'll stick with =(
> I'm on the spectrum, and I can't tell 99% of these things apart. Looks like a sad face to me. no different then the 500 other sad face emoji's I find. I'll stick with =( If it's any consolation, I don't think anyone could infer that from the emoji itself. The meaning is like a subculture's slang. I don't use emojis, so I only know the very basic ones (which I consider to be obfuscated emoticons).
It is pretty obvious that it is a face doing the sad puppy eyes, like the one a young niece might do after I refuse to buy her some ice cream. I didn't even know it's meant to be underground, impenetrable slang.
Re: 🥺: the best sudo replacement
#106Earlier quoted context omitted.
Speaking as the author of the work, most of _this post_ is satire meant to make you think about the existing security boundaries involved in privilege escalation. It is a false problem. The part about being annoyed that sudo is still written in C is coming from a sense of exasperation that there's still more predictable memory safety bugs involved with sudo because it's still written in C. The comment about python-cr…
[flagged]
Re: 🥺: the best sudo replacement
#107Re: 🥺: the best sudo replacement
#108For some more serious alternatives, I have heard of many people finding doas to be a drop in replacement. Furthermore, I've heard some people suggest neither doas nor sudo, but instead using an SSH server to gain root access to your local machine. It could listen on localhost and use key-based auth to allow root logins...
Except the enterprise security industry is waging war on ssh keys and ssh/sshd.
Re: 🥺: the best sudo replacement
#109Re: 🥺: the best sudo replacement
#110[flagged]