Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Run0, a systemd based alternative to sudo, announced

mastodon.social

Post reply on HN
Print view View original

301–310 of 902 posts

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

#301

Post by agwa »

abridgett wrote: post #178

I'm not sure it can replace non-trivial setups - sudo/doas looks set to stay. e.g when you need to restrict a set of users to run only certain applications with certain other users. sudo can do this (even if the config format can be painful).

Good news! run0 will use polkit[1], which uses JavaScript for its rules[2], so there's no limit to how complex your rules can get!

On the other hand, maybe adding a JavaScript interpreter to Linux's trusted computing base isn't good news...

[1] https://mastodon.social/@pid_eins/112353420303876549

[2] https://www.freedesktop.org/software/polkit/docs/latest/polk...

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

#302

Post by gcbirzan »

Arnavion wrote: post #189
withinboredom wrote: post #184

I don't understand the point of creating an entirely new shell inheriting almost nothing. Seems like that would cause a lot of issues (i.e., sudo make install)

That's how sudo already works on most (all?) distros. Eg Debian 12 has: Defaults env_reset ... which will clear almost everything that `make install` would've used. OpenSUSE TW has: Defaults always_set_home Defaults env_reset Defaults env_keep = "LANG LC_ADDRESS LC_CTYPE LC_COLLATE LC_IDENTIFICATION LC_MEASUREMENT LC_MESSAGES LC_MONETARY LC_NAME LC_NUMERIC LC_PAPER LC_TELEPHONE LC_TIME LC_ALL LANGUAGE LINGUAS XDG_SES…

If you're using autoconf/automake, you don't need to do that.

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

#303

Post by gh02t »

Karellen wrote: post #175
NekkoDroid wrote: post #166

Earlier quoted context omitted.

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…

It was a bit unclear to me from the thread, is there a persistent configuration option for this? I like the idea of tinting the terminal, but I also want to be able to turn it off with a global config option rather than having to type out a --background flag every invocation.

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

#304

Post by aftbit »

kbar13 wrote: post #45

systemd 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…

Ah yes I remember back when you just put the system hostname in /etc/hostname. Now we have hostnamed!

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

#305

Post by zamadatix »

Karellen wrote: post #175
NekkoDroid wrote: post #166

Earlier quoted context omitted.

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…

I think it's more that the default seems backwards than the lack of ability to change it.

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

#306

Post by byteknight »

shrimp_emoji wrote: post #238
byteknight wrote: post #220

Earlier quoted context omitted.

I really think you need some time away from a PC. You seem to be taking this incredibly personally. You can feel how you feel about the general public, but knowingly and willfully staying in a bubble is only detrimental to yourself. You will ultimately become what you hate. A person unwilling to move with the current change of society.

What if the current change of society is bad? E.g., see all of web development Also "time away from a PC" is ironic given "the current change of society". :p

I can strawman an argument too. But in reality you know exactly what I meant.

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

#307

Post by nialv7 »

StimDeck wrote: post #22

Just a reminder that there are plenty of systemd-less distros available. Also a reminder that those distros would have been safe from the nearly-solar-winds-level backdooring of Linux distros from XZ utils.

Can you even hear what you are saying? Don't you find it ridiculous to blame the XZ backdoor on systemd, instead of the actual hacker?

Even if systemd did not exist, the hacker would have just picked something else to infiltrate.

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

#308

Post by zamadatix »

gh02t wrote: post #303
Karellen wrote: post #175

Earlier quoted context omitted.

> 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…

It was a bit unclear to me from the thread, is there a persistent configuration option for this? I like the idea of tinting the terminal, but I also want to be able to turn it off with a global config option rather than having to type out a --background flag every invocation.

Aliasing the command as the command + your default arguments is the easiest general solution to this kind of problem. I'm not sure if there is a "systemd way" to permanently set it though.

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

#309

Post by mdaniel »

saghm wrote: post #278
lolinder wrote: post #249

Earlier quoted context omitted.

> I could `tail -f *.logs`. I remember how I didn't need to remember about `--no-pager` and `--follow`. journalctl supports -f, which by your own account you were already using for tail, so I'm not clear what's worse there. > I remember how I didn't have to google how to find logs between 10 days ago and 4 days ago, because the logs would be in a .tar created by logrotate with a date in the filename. My memory of thi…

> journalctl supports -f, which by your own account you were already using for tail, so I'm not clear what's worse there Yeah, this is a bit of an odd complaint. If I were this bothered by having to type those, I'd just make an alias to "journalctl --follow --nopager"` and would have forgotten about it years ago.

> I'd just make an alias to "journalctl --follow --nopager"` and would have forgotten about it years ago.

You sure would have forgotten about it when you tried to get onto another machine without the magic set of aliases

I am also prepared for someone to chime in that "log egress tools exist" to move up the Maslow's Hierarchy of Log Needs

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

#310

Post by airocker »

I have seldom come across unix multiuser environments getting used anymore for servers. Its generally just one user on one physical machine now a days. I understand run0's promise is still useful but i would really like to see the whole unix permission system simplified for just one user who has sudo access.
Post reply on HN