Systemd can't handle the process privilege for username startswith number
1–10 of 63 posts
Re: Systemd can't handle the process privilege for username startswith number
#2Re: Systemd can't handle the process privilege for username startswith number
#3I don't understand how this could be considered not a bug. Clearly, the unit was intended to run as 0day, not root. I must be missing something.
Re: Systemd can't handle the process privilege for username startswith number
#4I don't understand how this could be considered not a bug. Clearly, the unit was intended to run as 0day, not root. I must be missing something.
The rationale seems to be: "you're going to run into a lot of other software that'll also fail". He mentions xinetd as an example.
Re: Systemd can't handle the process privilege for username startswith number
#5Re: Systemd can't handle the process privilege for username startswith number
#6Sadly trolls already forced the issue locked but i feel like a sensible thing to do would be to keep that behavior but change the default user for parsing errors from root to nobody.
Systemd is running something as root because it doesn't like something in configuration file, instead of returning error or running it under the correct user. That's a huge WTF and a possible security issue, but alas. Systemd doesn't make mistakes and everything is someone elses fault.
Re: Systemd can't handle the process privilege for username startswith number
#7Sadly trolls already forced the issue locked but i feel like a sensible thing to do would be to keep that behavior but change the default user for parsing errors from root to nobody.
Re: Systemd can't handle the process privilege for username startswith number
#8Sadly trolls already forced the issue locked but i feel like a sensible thing to do would be to keep that behavior but change the default user for parsing errors from root to nobody.
Re: Systemd can't handle the process privilege for username startswith number
#9Why he said 0day not valid user?
I create '0day' user on my computer without problem (Fedora 26 Beta, Debian 9)
useradd 0day $ id 0day uid=1003(0day) gid=1003(0day) groups=1003(0day)