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

Re:Systemd can't handle the process privilege for username s... by db48x on Sunday July 02, 2017 @09:32AM (#14682400)

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

[ Parent | on HN ]

Re:Systemd can't handle the process privilege for username s... by CodeWriter23 on Sunday July 02, 2017 @03:26PM (#14683934)

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.

[ Parent | on HN ]

Re:Systemd can't handle the process privilege for username s... by digi_owl on Sunday July 02, 2017 @11:54AM (#14683040)

And?

What is going on here is that an admin thinks he has shored up the service defined in the service file, because hey, it runs. Only to later have the server 0wned because apparently it was running as root the whole time...

[ Parent | on HN ]

Re:Systemd can't handle the process privilege for username s... by chronid on Sunday July 02, 2017 @04:12PM (#14684127)

Breaking expectations is not a reasonable default.

[ Parent | on HN ]

Re:Systemd can't handle the process privilege for username s... by falcolas on Sunday July 02, 2017 @09:44AM (#14682462)

There are also user-level unit files; can this bug be triggered by those?

EDIT: No; it acts as if the 'User=' directive doesn't exist.

[ Parent | on HN ]