summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2020-08-11Sync with upstreamHEADmasterSteffen Nurpmeso
2019-06-20Revert the former, 3.5 shipped without it, so it is not neededSteffen Nurpmeso
2019-04-30crux-patch.diff: tweak last import: CRUX needs less restrictive approach yetSteffen Nurpmeso
2019-03-23crux-patch.diff: sync..Steffen Nurpmeso
The new S-S-D would not work with CRUX since for example exim uses a PID file with root:mail and then there is a root!=mail mismatch. The manual says Warning: using this match option with a world-writable pidfile or using it alone with a daemon that writes the pidfile as an unprivileged (non-root) user will be refused with an error (since version 1.19.3) as this is a security risk, because either any user can write to it, or if the daemon gets compromised, the contents of the pidfile cannot be trusted, and then a privileged runner (such as an init script executed as root) would end up acting on any system process. Using /dev/null is exempt from these checks. The actual code contradicts this as the mail group in our example cannot write the PID file, only read it. I thus have adjusted the code to only refuse the operation if the group can write the file, too. (Maybe this is even a "bug" that should be reported upstream?)
2019-03-23start-stop-daemon.8: import 2019-03-10 typo fixSteffen Nurpmeso
2019-03-23Sync with dpkg 1.19.5Steffen Nurpmeso
2019-03-23Sync with dpkg 1.19.4Steffen Nurpmeso
2019-03-23crux-patch.diff: adjust for latest syncSteffen Nurpmeso
2019-03-23Sync with dpkg 1.19.3Steffen Nurpmeso
2019-03-23crux-patch.diff: adjust for latest syncSteffen Nurpmeso
2019-03-23Sync with Debian Salsa [31ba2b1b10cfcc2149bb43fe9b918355177e4341], 2018-08-01Steffen Nurpmeso
2017-08-19added crux patchFredrik Rinnestam
2017-08-19initial commitFredrik Rinnestam

Generated by cgit