11 Commits

Author SHA1 Message Date
ac2a198056 crux-patch.diff: adjust version number 2023-01-05 11:49:08 +01:00
c037bdfb89 sync dpkg 1.21.13, Mon, 19 Dec 2022 02:07:45 +0100 2022-12-19 22:20:38 +01:00
6209edbd1d crux-patch.diff: adjust version date 2021-04-17 22:57:49 +02:00
c0282fa35a crux-patch.diff: sync 2021-01-09 22:25:49 +01:00
c4902c40c3 Sync with upstream 2020-08-11 16:37:31 +02:00
31401da642
Revert the former, 3.5 shipped without it, so it is not needed 2019-06-20 15:52:59 +02:00
4ddd21fc6d
crux-patch.diff: tweak last import: CRUX needs less restrictive approach yet 2019-04-30 23:56:58 +02:00
8c845d1646 crux-patch.diff: sync..
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-23 07:16:12 +01:00
22c6dea592 crux-patch.diff: adjust for latest sync 2019-03-23 07:16:12 +01:00
1419c791d0 crux-patch.diff: adjust for latest sync 2019-03-23 07:16:12 +01:00
Fredrik Rinnestam
28b8bdb288 added crux patch 2017-08-19 18:43:03 +02:00