Comment by charcircuit
Comment by charcircuit a month ago
>For example, the core-dump handler is launched by the kernel as a user-mode helper, meaning that it runs fully privileged in the root namespace.
Why is it not run as a dedicated core dump user?
>the core-dump socket to a helper can be intercepted
There have been several vulnerabilities related to this feature of passing core files to a container. I question if this feature is actually worth it considering one probably wants to have shared infrastructure for crash reporting anyways.
> Why is it not run as a dedicated core dump user?
You could imagine an API that sets the UID of this user, and the kernel could easily run the coredump handler as that user, but the kernel can't so easily automate the creation of a complicated namespace to contain that process (and the process can't do it itself because it could be exploited before it gets around to it). Look at the code in runc some time to see how complicated setting up a namespace has got.
> one probably wants to have shared infrastructure for crash reporting anyways
Not really on a single machine. coredumpctl actually works very well for solo development, I use it all the time.