This will be great. We can finally deprecate sudo on systemd systems. Then we should be able to deprecate PAM, setuid bit, etc.
I wonder, are there any distros already with a nosuid root?
Run0, a systemd based alternative to sudo, announced
161–170 of 902 posts
Re: Run0, a systemd based alternative to sudo, announced
#162Earlier quoted context omitted.
I'd agree with your message if systemd was just an init system.
It's not difficult to use some parts of systemd without using others. Is it any different than something like coreutils, another package of linux utilities that are synergistic but usable seperately? Nobody complains about coreutils being bundled. Even the rewrite in rust crowd bundle them.
It really is not. This "sudo replacement" (which under the hood is systemd-run) will apparently require quite a bit of the systemd stack to operate. That is not something you have access to in many lightweight container distros or on other non-systemd distros.
And coreutils is expected because most people use GNU/Linux. Coreutils is that GNU userland part. And either way, the majority of coreutils are GNU implementations of standard unix components. You can use most software that depends on coreutils on other *nix platforms like BSD for this reason.
Re: Run0, a systemd based alternative to sudo, announced
#163[flagged]
You're always welcome to write an alternative if you don't think systemd's direction is correct. Frankly with the number of detractors you could likely form a much larger team to "do it properly" instead! Love or hate Pottering and his team, they're at least writing code instead of postulating on internet forums. systemd's adoption and popularity among many is proof of that
> instead of postulating on internet forums
Love or hate internet discussion, you're always welcome to not participate in it.
Re: Run0, a systemd based alternative to sudo, announced
#164Earlier quoted context omitted.
And people are also telling you that tight integration is not a mandate. Having a bunch of stuff designed to work together does not mean that they're tightly coupled and can only work with their specific implementations. We've all got confirmation bias, the trick is to be aware of it.
This is such a bizarre statement. Of course any system with tight integration demands more precise specifications. Literally systems engineer 101. This is such an absurd hill to die on.
You aren't making any sense. All of the components of system D are separate programs, and yes they are maintained by the same general project and designed to integrate well with each other, but just because components are designed to integrate well with other components from the same project if they are present, that doesn't remotely mean that all of the components are required. And I mean, the proof is in the pudding, there are plenty of distros that do not use all of the components of systemd. Also, doesn't Linux have a long history of creating integrated suites of programs designed to integrate well with each other and used together? Like GNU?
Re: Run0, a systemd based alternative to sudo, announced
#165Piece by piece, Red Hat is taking over the Linux ecosystem.
Well, they're the only ones actually funding development of the ecosystem, aren't they?
The rest just do a lot of opinoning and complaining and not that much of developing.
Re: Run0, a systemd based alternative to sudo, announced
#166Overall, this seems great. However... > [...] by default it will tint your terminal background in a reddish tone while you are operating with elevated privileges ?!! ouch ... seems orthogonal to the actual important parts. Disclaimer: I didn't try it.
I tried it a bit ago (when it was still called uid0, pre-release), I also wasn't a fan of the tinting.
I like the intent behind it, but some terminals already tint the header color when running sudo, I haven't tested if its done specifically for sudo or if its in a more generic way that could handle this as well.
Re: Run0, a systemd based alternative to sudo, announced
#167Piece by piece, Red Hat is taking over the Linux ecosystem.
Well, they're the only ones actually funding development of the ecosystem, aren't they? The rest just do a lot of opinoning and complaining and not that much of developing.
The implicit premise of this comment is that linux is broken and needs to be changed. It isn't. The changes are not inherently good. Development is not inherently good. Just look at Gtk3 from 2014 to 2024. It was far more functional in 2014 (re: keyboard input) and now that has been removed because "progress".
Re: Run0, a systemd based alternative to sudo, announced
#168I asked this in a thread about this from last night and didn't get a reply. For context, the way "run0" works is to apparently send a signal to polkit that requests a command under the root user's ID and permissions, thereby getting a privileged shell without SUID:
> How hard would it be to create a program to send a signal to polkit "impersonating" run0 and obtain a root shell without entering a password?
Anybody know how this is being authenticated?
Re: Run0, a systemd based alternative to sudo, announced
#169systemd has been a net positive for the linux ecosystem. remember when you had to write bash scripts to start, stop, restart services and handle any other signals you want to send it? nowadays it's a unit file (basically just an ini file) away with relatively straightforward API. and you can actually declare startup dependencies and other useful relationships past just "prepend a number signifying when it should run…
Yeah, basically I've found that the people the more vocal against systemd are either not really knowing how it works behind the scenes, and just criticizing for the sake of it (or because other people do so), or criticizing from an ideological point of view (do one thing and do it well). They see systemd as an octopus, not following the unix ideology. Which I don't really agree tbh
The issue is that it's not just ideological. "Do one thing and do it well" is important because if you want to port software to another platform, it's a lot easier to port a single dependency component over to make it work than it is to port over the entire framework.
This is a serious problem and it makes it way harder to make things cross platform.
Re: Run0, a systemd based alternative to sudo, announced
#170Piece by piece, Red Hat is taking over the Linux ecosystem.
I guess but in this case it's doing something that sudo doesn't do — get privs from a daemon instead of setuid, and using something that systemd already did (systemd-run).
Is it that weird that they would make a runas frontend when all the pieces of it were lying around?