Hacker News Reader

Comment by isatty | Hacker News Reader

What I saw was poettering spouting garbage about what he thinks is an invalid user name (when in reality, it is not and common tools like useradd don't complain about it).

As the owner for a critical service like systemd (I don't use it, I prefer openRC on gentoo), he should know better.

View on HN

grrr... your init system should not dictate what a valid username is. Your init system should use whatever users you've configured.

I don't like your name. Therefore you get root.

How on earth did this init system become so prevalent?

There was a whole hoo-hah in Debian over what to replace System 5 rc with: upstart, OpenRC, systemd, or something else. It got raised to the Technical Committee, sparked several resignations, went to a vote of the entire Debian Developer membership, and lasted for a long time.

* http://jdebp.eu./FGA/debian-systemd-packaging-hoo-hah.html

The Arch process was rather different:

* https://news.ycombinator.com/item?id=11834348

The Debian people did look at who develops the various systems, but they mainly just measured the developer count and what else was on each bandwagon. (See section 3.3 in Russ Allbery's evaluation, for example.) They didn't make any deeper evaluation extending to things such as the way that bugs got responded to in practice or what design steps people were taking to limit bugs.

Neither process was extensive enough to have spotted a User=0pointer gives superuser rights bug.

I was just venting... and you provided a great answer to my rhetorical question - which I found very interesting by the way.

I didn't see Russ' evaluation, but I get the point.

> your init system should not dictate what a valid username is

systemd is a task manager (which happens to manage init along with everything else it can and often cannot). Referring to systemd as an init system is just muddying well-tread waters by people who are lazily misunderstanding the technical issues. The problem with usernames is that there is no standard so schemes are OS specific. It's not really a systemd problem at the core. The systemd problem (because it almost always is badly implemented) is that it uses it's own username validation scheme that defaults to permissive root when the systemd scheme is not matched for configured services. Running on top of heterogeneous environments, you get inconsistent behavior (even when you comply with the OS). This would be like apache spawning handler threads as root if it doesn't like the username it's configured to run as, regardless if the username is valid under OSX and invalid under Fedora. Too bad, username schemes are now dictated by systemd, is Poettering's position.

The problem with usernames is that there is no standard

Yes there is: https://github.com/systemd/systemd/issues/6237#issuecomment-...

I'll just say that I strongly disagree. Pointing to the IEEE compatibility standard is being misleading. That's part of a standard and is not adequately inclusive to be considered "the standard". OS's that systemd supports do not all follow the POSIX standard. i.e. "not officially certified as POSIX compatible, comply in large part". Practically, this means some are more strict and other less so.

In regard to usernames, I can definitely forgive Poettering's initial failure in design to confusion. His assertion that he is following "the standard" fails on both a practical and logical level.

I am having a very hard time following your logic. You made an assertion about there being no standard for usernames. I pointed you to some info someone wrote in the relevant issue on Github regarding what POSIX asserts usernames should conform to, with POSIX being generally accepted to be a standard for *nix type OS's. Your response appears to boil down to "But POSIX doesn't count because not all distro's are POSIX certified"

POSIX counts, for POSIX systems. There is no standard for systemd supported systems. The logic is straightforward, like the reality.

Reply on news.ycombinator.com