5 ms·
I 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
by bee_rider 4y ago
I 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-month language to reimplement their old projects. Maybe if there were some folks who knew rust and were interested in doing this kind of work it would get done.
- lilyball 4y agoThe quoted paragraph has nothing to do with language choice.
- bee_rider 4y agoThey 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 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 because then 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. So, I guess fair enough. I will expand it slightly to say: it is an uncharitable way of describing volunteers who don’t feel like learning a new language and reimplementing their old projects while also overturning a huge ecosystem of software.
- chaxor 4y agoIt's obviously a (failed) attempt to be funny by being very sarcastic. No one is stupid enough to this that writing it in Rust was even an option in the days unix was written - especially considering the types of people that would know how to write C and Rust for kernels.
- 59nadir 4y agoThey do believe it should be rewritten in Rust: > 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.
- mid-kid 4y agoThe paragraph quoted is about the language choice, too, just that part was snipped off because it's long. It's one ball of a paragraph that goes in all directions, citing debian and gentoo's troubles with rust support[1] and calling them leeches for wanting to support obscure architectures. Not a fun read. [1]: https://lwn.net/Articles/845535/ https://lwn.net/Articles/845535/
- adenozine 4y agoRust? Well, speaking of egotistical open source people that refuse to change...
- hot_gril 4y agoHeh. I get what you're saying, but I feel that vibe much more from Golang than from Rust. Rust seems down to earth.
- SLWW 4y agoI do think it's funny how this is the only comment in the thread that isn't greyed out. I wonder if there would be a way to lose the 'value' of a downvote if the account in question predominantly downvotes a specific opinion too much (a form of abuse i think). The assumption being that, "ok, you downvoted three posts, that were all very incendiary; though the other 40+ you've downvoted were all that way, statically the chance that those posts are all offensive is unlikely." Would be interesting to see; I don't hate Rust, but I don't appreciate the zealous nature of most of their advocates, and for me personally, there's nothing fun about writing in Rust. It's also a bit too bloated for my tastes, i would never want to run it in lowlevel personally. Yet most of the time I stay away from threads talking about Rust, because i just get sent to the bottom fairly quickly, on most sites that encourage discussion.
- adenozine 4y agoI mean, I heard it put this way and it has always stuck with me: every conversation here is implicitly inclusive of @dang. He’s wholly responsible for the vibes at large, and in the past several years it has become blindingly clear that he has no issues or qualms with Rusticles overtaking any thread they choose. I could write a scathing 10k word treatise on any topic with a single pithy remark about Rust in it somewhere and he’d allow the discussion to be dominated by the Rust tangent that would inevitably multiply in the comments here. The chilling effect is as you describe, that I often feel discouraged from contributing my knowledge, experience or opinions because of the blatant manipulation of conversations by Rusticles and the apparently contentedness by dang for that to be the defining angle of discussion here. HN should have tags. Every article gets tagged by users with high karma counts, by some sort of ranked consensus (maybe a rust tag, python tag, database tag, politics tag, etc) and users could just list tags they want muted in their settings. Instead, I’ll be told about the HN guidelines and some minutia in this comment that is somehow worse than a thousand idiots hijacking literally every conversation about a particular topic. As they say, not my monkey, not my circus…
- tristor 4y agoHonestly, I don't think you should take anything the author of this wrote seriously, the most charitable interpretation is that most of their work is a form of satire.
- xena 4y agoSpeaking 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-cryptography failing to move to Rust because of random Gentoo uses holding it back was from a sense of exasperation that we can't have "nice things". I'm tired of having to emergency patch everything because we as an industry can't make our fundamental security tools _measurably safer_ with languages like Rust. I am a lot more serious in my other posts (such as this one: https://xeiaso.net/blog/2022-media https://xeiaso.net/blog/2022-media or this one: https://xeiaso.net/blog/hlang-nguh https://xeiaso.net/blog/hlang-nguh), but sometimes I have to write satirical things otherwise people won't get the point. Believe what you want though.
- hot_gril 4y agoI feel that where I work. I'm outnumbered in wanting to write web servers with high-level, non-performance-sensitive business logic in something other than C++. We keep having memory safety problems, but more importantly, it's really slow to develop this way and doesn't match the skillset we're hiring. However, these people are being paid. The common reason our most senior engineers tell me isn't even that it's too late to switch, it's that "C++ is perfectly fine as long as you use it right" and "it doesn't matter what the outside world uses" and "performance."
- archgoon 4y ago[dead]
- ilyt 4y ago[flagged]
- brundolf 4y agoIt wasn't very charitable, but neither is the "flavor-of-the-month language" dig
- bee_rider 4y agoThat’s fair, it was a bit rude of me. Sorry rust folks it actually is a cool language.
- ripley12 4y agoOdd that you left off the rest of that quote ("...because then 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") which links to: https://lwn.net/Articles/845535/ https://lwn.net/Articles/845535/ > Maybe if there were some folks who knew rust and were interested in doing this kind of work In this specific example, "this kind of work" would involve porting Rust to 5+ obsolete CPU architectures. Not exactly rewarding work.
- bee_rider 4y agoThat it is not very rewarding seems like a much more synpathetic and likely reason than egotism.