On Wed, Feb 17, 2016 at 02:15:24PM -0600, Eric W. Biederman wrote: > Mateusz Guzik <mguzik@xxxxxxxxxx> writes: > > On Tue, Feb 16, 2016 at 07:33:39PM +0800, Zhao Lei wrote: > >> For container based on namespace design, it is good to allow > >> each container keeping their own coredump setting. > > > > Sorry if this is a false alarm, I don't have easy means to test it, but > > is not this an immediate privilege escalation? > > It is. This is why we do not currently have a per namespace setting. > Thanks for confimation. > Solving the user mode helper problem is technically a fair amount of > work, if not theoretically challenging. > Well, I would say custom core_patterns without pipe support are still better than none. Say one would ensure a stable core_pattern (i.e. that it cannot be modified as it is being parsed) and a restricted set of allowed characters in the pattern (which would not include the pipe), validated when one attempts to set the pattern. Does this sound acceptable? If so, and there are no counter ideas from Lei, I can get around to that. -- Mateusz Guzik _______________________________________________ Containers mailing list Containers@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linuxfoundation.org/mailman/listinfo/containers
