On Monday, 12 December 2016 at 20:54, Nicholas Miell wrote: [...]
systemd-coredump (or, rather, journald) ignores the split between system accounts and user accounts as configured in /etc/login.defs ("the authoritative definition of UID/GID space allocation", according to the Fedora wiki) and instead hard codes 1000 as the split*.
The end result is that when systemd-coredump enabled, unprivileged users cannot access their own core dumps. (Or any of their own logs in journald.)
This means that if you are a loyal Fedora user that initially installed before the change from 500 to 1000 (Fedora 15 or earlier) and have been faithfully upgrading from release to release, enabling systemd-coredump by default in Fedora 26 will be a regression in functionality.
systemd-coredump should not be enabled by default in Fedora until this bug is fixed by the systemd developers.
*: It's actually more egregious than that: /etc/login.defs is parsed on the build machine at compile time and the extracted value is hard coded into the various systemd executables which then completely ignore /etc/login.defs at run time.
Have you filed a bug (preferably upstream)? If yes, please share the bug number and comment in the FESCo ticket (https://pagure.io/fesco/issue/1654).
Regards, Dominik