Messages in this thread | | | From | Andy Lutomirski <> | Date | Wed, 18 Mar 2015 14:39:00 -0700 | Subject | Re: seccomp vs ptrace |
| |
On Wed, Mar 18, 2015 at 2:30 PM, Serge E. Hallyn <serge@hallyn.com> wrote: > Hi, > > I'm writing to ask about > > The seccomp check will not be run again after the tracer is > notified. (This means that seccomp-based sandboxes MUST NOT > allow use of ptrace, even of other sandboxed processes, without > extreme care; ptracers can use this mechanism to escape.) > > This basically means that seccomp cannot be safely used with for instance > an upstart based container. I've been told that Andy was working on > changing the order so that ptrace checks would be done before seccomp. > Is there any update on that? Is it likely to happen? Scrapped?
No, just got stalled because I'm too busy. The code is here:
https://git.kernel.org/cgit/linux/kernel/git/luto/linux.git/log/?h=x86/seccomp
but it's not really adequately tested.
> > thanks, > -serge
-- Andy Lutomirski AMA Capital Management, LLC
| |