That's good to hear.
Memory-safe sudo to become the default in Ubuntu
31–40 of 282 posts
Re: Memory-safe sudo to become the default in Ubuntu
#32Seems like the trifecta group is /just/ about migrating tools to rust? Am I understanding that right? I don't have a problem with it, specifically. Seems odd that they don't advertise it, though.
[flagged]
Not like GNU is any less religious...
I think they just want to ditch GNU tools and lots of young, low level programmers want to use Rust (same rationale for Linus accepting Rust code into the kernel).
Re: Memory-safe sudo to become the default in Ubuntu
#33Earlier quoted context omitted.
Sudo had quite a few problems with security, partially because of this doas was developed for BSD. Some problems come from the huge amount of features(ldap, easter eggs, ...). sudo-rs reduces the problems by not implementing those features.
Removing LDAP is a huge problem for the more important sudo deployments though: centralized management of permissions is kind of a vital function.
Could you clarify what you mean by more important sudo deployments?
Re: Memory-safe sudo to become the default in Ubuntu
#34Earlier quoted context omitted.
We've accepted it at this point, but I wonder if the religious element of GNU tools and free software in general was as contentious way back when.
A little while ago I realized with a start that it's been years since I've heard anyone angrily insist on calling it "GNU/Linux", when that was constant background noise during the Slashdot era. One of those old fights that just faded away, I guess.
Oh yeah, I got to meet Stallman at a book signing when I was like 17, and like an idiot happened to wear a "Linux" shirt.
I genuinely hadn't thought of this point of contention beforehand, but oof he did not care for that.
Re: Memory-safe sudo to become the default in Ubuntu
#35Seems like the trifecta group is /just/ about migrating tools to rust? Am I understanding that right? I don't have a problem with it, specifically. Seems odd that they don't advertise it, though.
The other big thing iirc is they’re all MIT licensed rather than GPL(et variants) licensed
Sudo is permissively licensed. https://www.sudo.ws/about/license/
Re: Memory-safe sudo to become the default in Ubuntu
#36Earlier quoted context omitted.
[flagged]
> The religious element It is only "religious" if you think it in such a way. I'd say the amount of skepticism (rather than valid criticism) has been no less than enthusiam in the community. As the saying goes, there are two kinds of languages...
[flagged]
Re: Memory-safe sudo to become the default in Ubuntu
#37Did sudo have memory problems? Did it ever fail because it didn't handle its memory correctly?
Re: Memory-safe sudo to become the default in Ubuntu
#38Earlier quoted context omitted.
A little while ago I realized with a start that it's been years since I've heard anyone angrily insist on calling it "GNU/Linux", when that was constant background noise during the Slashdot era. One of those old fights that just faded away, I guess.
Oh yeah, I got to meet Stallman at a book signing when I was like 17, and like an idiot happened to wear a "Linux" shirt. I genuinely hadn't thought of this point of contention beforehand, but oof he did not care for that.
Did you tell him you were a fan of just the kernel, not the userland?
Re: Memory-safe sudo to become the default in Ubuntu
#39Earlier quoted context omitted.
> The religious element It is only "religious" if you think it in such a way. I'd say the amount of skepticism (rather than valid criticism) has been no less than enthusiam in the community. As the saying goes, there are two kinds of languages...
[flagged]
[flagged]
Re: Memory-safe sudo to become the default in Ubuntu
#40Earlier quoted context omitted.
There's value in always starting processes from a known-secure environment rather than attempting to transform a user's arbitrary environment into a secure one.
True, CVE-2021-4034 comes to mind as a recent example (exploiting zero-length argv)
How is that any different than a daemon that has a parser error in its message handler, except that the daemon could be misconfigured to listen on a network socket?
The original unix process abstraction was extremely simple; the entire spec is a few pages.
The problem is that Linux keeps adding more and more levels of Rube Goldberg machine to its security model, so now literally no one understands how a default minimal install of, say, Ubuntu works.
Adding a magic daemon that runs stuff as root to this pile of complexity probably won’t help. Ripping out almost all the cruft that’s accumulated over the years, and adding back something sane (maybe BSD jails) would work a lot better.