The apt-cacher-ng init script gives ownership of its PID file directory to its runtime user. That can be exploited by the apt-cacher-ng user to kill root processes, since when the service is stopped, root will send a SIGTERM to the contents of the PID file (which are controlled by the "apt-cacher-ng" user). References: https://bugs.gentoo.org/631878
Created apt-cacher-ng tracking bugs for this issue: Affects: epel-7 [bug 1500085] Affects: fedora-all [bug 1500084]
Upstream's debian/apt-cacher-ng.init has the issued script. Fedora RPM does not use it as using systemd service rather than init.d script. Actually the script does not even include the RPM package. From this, I am closing this bug ticket.
I was perusing this and i noticed a commit referencing this bz here: https://src.fedoraproject.org/rpms/apt-cacher-ng/c/ad4e4a0613c9f314e214afabb4c52c70e5863976?branch=master You might want to add a /usr/lib/tmpfiles.d/apt-cacher-ng.conf snippet for /run/apt-cacher-ng as /run is on a tmpfs and user apt-cacher-ng will not be able to create /run/apt-cacher-ng.