Systemd can't handle the process privilege for username startswith number • Hacker News Board

Re: Systemd can't handle the process privilege for username startswith number

#61

Post by digi_owl » Sun, Jul 02, 2017, 4:05 PM UTC

rndgermandude wrote: post #25

hahainternet wrote: post #19

Earlier quoted context omitted.

> "Trolls" have not forced anythings - just standard systemd developer behavior. They've had to delete multiple posts from the thread which are nothing but trolls, hell YOUR post is nothing but a troll.

This is not true, I've seen the issue develop till it was closed. There were like 2 posts removed, 1 might have been trollish, the other(s) were just people voicing displeasure at general systemd dev behavior. That might be offtopic and not polite, but it's not a troll either. And the OP you're replying to falls into that snarky, impolite category too, but is not a troll.

sadly these days it is all too easy to stick fingers in ears and go "troll troll troll" or "hater hater hater" than actually introspect.

Tempted to label it as a ripple effect of the rising SJW element in FOSS, because both terms seems to attract that group in defense of the shouter without concern for context.

Re: Systemd can't handle the process privilege for username startswith number

#62

Post by CodeWriter23 » Sun, Jul 02, 2017, 7:26 PM UTC

db48x wrote: post #54

ArneBab wrote: post #43

Earlier quoted context omitted.

They just would have had to think "let’s do the safe thing — instead of just assuming everything goes well and potentially using the root user as fallback if we’re wrong". It’s a mindset/philosophy problem, and that doesn’t change when bugs get fixed. It would require the devs to change, but that didn’t happen in the past decade, so we cannot just assume that it will happen in the next.

But you have to be root to install a systemd unit in the first place...

Doesn't mean I want systemd silently escalating my process to root when I think I've told it to contain privileges of the process to a specific userid. Clearly the correct behavior for such a program is to throw an error if it is rejecting a username for ANY reason, even when that reason is supported by stilted reasoning.

Re: Systemd can't handle the process privilege for username startswith number

#63

Post by chronid » Sun, Jul 02, 2017, 8:12 PM UTC

db48x wrote: post #54

ArneBab wrote: post #43

Earlier quoted context omitted.

They just would have had to think "let’s do the safe thing — instead of just assuming everything goes well and potentially using the root user as fallback if we’re wrong". It’s a mindset/philosophy problem, and that doesn’t change when bugs get fixed. It would require the devs to change, but that didn’t happen in the past decade, so we cannot just assume that it will happen in the next.

But you have to be root to install a systemd unit in the first place...

Breaking expectations is not a reasonable default.