Live data from Hacker News

Run0, a systemd based alternative to sudo, announced

mastodon.social

171–180 of 902 posts

Re: Run0, a systemd based alternative to sudo, announced

#172
post #165

Earlier quoted context omitted.

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".

Nobody needs to adopt the changes. Everybody did because it's better than the alternatives. There are still systemd-less distros if you like it.

Re: Run0, a systemd based alternative to sudo, announced

#174
post #158

Earlier quoted context omitted.

I can see creating a system with zero setuid files, but I don't think this reduces PAM use, does it?

Not setuid generically, but `sudo` itself has a bunch of pam support/dependency.

I would expect sudo to also touch pam a lot, but AIUI systemd also uses pam through polkit for its ~native permission system - https://serverfault.com/questions/841306/authentication-is-r...

Re: Run0, a systemd based alternative to sudo, announced

#175

Overall, 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.

> I also wasn't a fan of the tinting.

From the linked mastodon thread:

> For example, by default it will tint your terminal background in a reddish tone while you are operating with elevated privileges. That is supposed to act as a friendly reminder that you haven't given up the privileges yet, and marks the output of all commands that ran with privileges appropriately. (If you don't like this, you can easily turn it off via the --background= switch).

(emphasis mine)

Re: Run0, a systemd based alternative to sudo, announced

#176

This will be great. We can finally deprecate sudo on systemd systems. Then we should be able to deprecate PAM, setuid bit, etc.

Is removing setuid actually a win? I know it presents a security risk, but it feels like we're not actually removing that attack surface, just moving it around.

Re: Run0, a systemd based alternative to sudo, announced

#177
post #165

Earlier quoted context omitted.

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".

No one is stopping you from running a 2014 version of your favorite distro. Seems like a good way to address your concerns.
Post reply on HN