mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Serge E. Hallyn" <serge@hallyn.com>
To: lkml <linux-kernel@vger.kernel.org>,
	Kees Cook <keescook@chromium.org>,
	Andy Lutomirski <luto@amacapital.net>,
	stgraber@ubuntu.com
Subject: seccomp vs ptrace
Date: Wed, 18 Mar 2015 16:30:07 -0500	[thread overview]
Message-ID: <20150318213007.GA24393@mail.hallyn.com> (raw)

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?

thanks,
-serge

             reply	other threads:[~2015-03-18 21:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-18 21:30 Serge E. Hallyn [this message]
2015-03-18 21:38 ` Kees Cook
2015-03-18 21:42   ` Andy Lutomirski
2015-03-18 21:44     ` Kees Cook
2015-03-18 22:06       ` Andy Lutomirski
2015-03-18 21:39 ` Andy Lutomirski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150318213007.GA24393@mail.hallyn.com \
    --to=serge@hallyn.com \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@amacapital.net \
    --cc=stgraber@ubuntu.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®