On 2018-05-21 21:17, James Knott wrote:
On 05/21/2018 02:53 PM, Carlos E. R. wrote:
No, the user doesn't need to fiddle. Just access the directory where the dumps are stored, but currently he doesn't get permission.
Perhaps I'm missing something, but I thought giving mere mortals access to core dumps etc. was a security risk.
Not if it is your program which crashed. A developer needs access to his own crashes to debug them. A user may want to mail his crash data to a developer somewhere else. It is not giving the user access to coredumps of everybody, but only to his own coredumps. If you disable systemd intervention, and leave things as they were some years ago, the coredumps are left on the directory of the user and owned by the user. This has been so for decades, so not a security risk, IMHO. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)