On Sun, 2021-06-27 at 15:00 +0200, Michael Biebl wrote:
> I fail to see the security benefit here? What do we gain by (not)
> pre-allocating a system group like systemd-coredump?
Well it's not a big issue... but as always: something that is not even
there, may not be abused in the first place.
Am 26.06.21 um 20:40 schrieb Christoph Anton Mitterer:
On Sat, 2021-06-26 at 20:07 +0200, Michael Biebl wrote:
You can try to convince upstream to split up the (monolithic)
systemd.conf this way though.
I've asked them to consider this in:
https://github.com/systemd/systemd/issues/20044
On Sat, 2021-06-26 at 20:07 +0200, Michael Biebl wrote:
> Then systemd would just setup all groups that are used by systemd
> (and
> sub-packages).
Seems to be a good change... but it would then still set up *all*
users, whether the respective part is used or no.
> Personally, I don't think
Am 26.06.2021 um 17:38 schrieb Christoph Anton Mitterer:
Package: systemd
Version: 247.3-5
Severity: normal
Hey.
I was recently doing some manual cleanup of stale users/grous and since
the systemd-timesync and systemd-coredump users/groups a no longer created
by the systemd package itself
4 matches
Mail list logo
