Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Mon, 21 May 2012 11:40:29 -0700
From: Andrew Lutomirski <luto@....edu>
To: Roland McGrath <mcgrathr@...gle.com>
Cc: keescook@...omium.org, serge.hallyn@...onical.com, 
	Will Drewry <wad@...omium.org>, indan@....nu, Eric Paris <netdev@...isplace.org>, hpa@...or.com, 
	rdunlap@...otime.net, linux-security-module@...r.kernel.org, 
	kernel-hardening@...ts.openwall.com, markus@...omium.org, mingo@...hat.com, 
	eric.dumazet@...il.com, tglx@...utronix.de, pmoore@...hat.com, 
	peterz@...radead.org, oleg@...hat.com, coreyb@...ux.vnet.ibm.com, 
	corbet@....net, linux-kernel@...r.kernel.org, akpm@...ux-foundation.org, 
	eparis@...hat.com
Subject: Re: seccomp and ptrace. what is the correct order?

On May 21, 2012 8:25 PM, "Roland McGrath" <mcgrathr@...gle.com> wrote:
>
> From a security perspective I think the natural expectation would be that
> the seccomp check is on the values that will actually be used, without an
> intervening opportunity to change anything.

Certainly if the seccomp sandbox allows ptrace, this is important.

[Apologies if the Android app uses some evil mime type here.]

--Andy

Content of type "text/html" skipped

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.