On 8/13/2012 4:45 AM, Jarkko Sakkinen wrote:
> On Thu, Aug 09, 2012 at 05:46:38PM -0700, Casey Schaufler wrote:
>> On 12/20/2011 11:20 PM, Jarkko Sakkinen wrote:
>>> Allow SIGCHLD to be passed to child process without
>>> explicit policy. This will help to keep the access
>>> control policy simple
On Thu, Aug 09, 2012 at 05:46:38PM -0700, Casey Schaufler wrote:
> On 12/20/2011 11:20 PM, Jarkko Sakkinen wrote:
> > Allow SIGCHLD to be passed to child process without
> > explicit policy. This will help to keep the access
> > control policy simple and easily maintainable with
> > complex
On Thu, Aug 09, 2012 at 05:46:38PM -0700, Casey Schaufler wrote:
On 12/20/2011 11:20 PM, Jarkko Sakkinen wrote:
Allow SIGCHLD to be passed to child process without
explicit policy. This will help to keep the access
control policy simple and easily maintainable with
complex applications
On 8/13/2012 4:45 AM, Jarkko Sakkinen wrote:
On Thu, Aug 09, 2012 at 05:46:38PM -0700, Casey Schaufler wrote:
On 12/20/2011 11:20 PM, Jarkko Sakkinen wrote:
Allow SIGCHLD to be passed to child process without
explicit policy. This will help to keep the access
control policy simple and easily
On 12/20/2011 11:20 PM, Jarkko Sakkinen wrote:
> Allow SIGCHLD to be passed to child process without
> explicit policy. This will help to keep the access
> control policy simple and easily maintainable with
> complex applications that require use of multiple
> security contexts. It will also help
On 12/20/2011 11:20 PM, Jarkko Sakkinen wrote:
Allow SIGCHLD to be passed to child process without
explicit policy. This will help to keep the access
control policy simple and easily maintainable with
complex applications that require use of multiple
security contexts. It will also help to
6 matches
Mail list logo