upslog assumes starting as root, but should it? #1717
Assignees
Labels
service/daemon start/stop
General subject for starting and stopping NUT daemons (drivers, server, monitor); also BG/FG/Debug
Milestone
Comments
jimklimov
added
the
service/daemon start/stop
jimklimov
added a commit
to jimklimov/nut
that referenced
this issue
Jan 2, 2025
… writepid() calls by non-root programs [networkupstools#1717] Signed-off-by: Jim Klimov <[email protected]>
jimklimov
added a commit
to jimklimov/nut
that referenced
this issue
Jan 2, 2025
… writepid() calls by non-root programs [networkupstools#1717] Signed-off-by: Jim Klimov <[email protected]>
jimklimov
added a commit
to jimklimov/nut
that referenced
this issue
Jan 2, 2025
… writepid() calls by non-root programs [networkupstools#1717] Signed-off-by: Jim Klimov <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As analyzed in #1712 (comment) the
upslogdaemon is one of two that really usePIDPATHwhich may be owned byroot(rather thanALTPIDPATHwhich should be owned by unprivileged run-time account likenut).Code of this daemon writes the PID file and drops privileges, with mysterious comment
/* now drop root if we have it */-- this implies we might start not asroot, and then fail towritepid()(ifPIDPATHis root-owned like/var/run) and then tobecome_user(). It did so since beginning of time.Should the logging daemon start as
rootin the first place however?..The text was updated successfully, but these errors were encountered: