3 ms·
Err, there are such things as user level systemd unit files[0]. I have no idea if this bug gets triggered by those as well, but it's a pretty big deal if it is.
by falcolas 9y ago
Err, there are such things as user level systemd unit files[0]. I have no idea if this bug gets triggered by those as well, but it's a pretty big deal if it is.
> There's a new systemd bug that gets the haters aroused!
Oiy... I feel like I am walking into the middle of a Vim/Emacs flame war. Very unfortunate.
[0] https://www.freedesktop.org/software/systemd/man/systemd.unit.html#id-1.7.5 https://www.freedesktop.org/software/systemd/man/systemd.uni...
[EDIT] As noted downstream, the parsing error causes the 'User=' directive to just be ignored, so a user unit file will be run by the user. Still too many vectors of attack, sadly.
- joombaga 9y agoYeah, Mattias is super defensive in this. It doesn't help your cause to downplay serious vulnerabilities in the software you're championing. Anyone acting like this is a point for upstart/sysvinit/whatever is obviously misguided; there's no need to preempt that misguidance.
- the_mitsuhiko 9y ago> I have no idea if this bug gets triggered by those as well Why should it? The bug is not that it runs as root but that it encounters a parsing error and uses the default. The default for root is root and the default for user A is user A.
- falcolas 9y ago> Why should it? Thank you for the correct, if condescending, answer. It was unclear from the original bug, or this article, if it was falling back on a hardcoded 0 or the user used when the directive is not present. Since systemd's own behavior is inconsistent, I can't depend on that behavior to derive the reasonable answer. That inconsistency stems from the fact that a "valid" user name that doesn't exist triggers different behavior than an "invalid" user name; and the definition of "valid" is different between systemd and the rest of Linux.