From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757003AbbCRVaL (ORCPT ); Wed, 18 Mar 2015 17:30:11 -0400 Received: from h2.hallyn.com ([78.46.35.8]:48347 "EHLO h2.hallyn.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754880AbbCRVaJ (ORCPT ); Wed, 18 Mar 2015 17:30:09 -0400 Date: Wed, 18 Mar 2015 16:30:07 -0500 From: "Serge E. Hallyn" To: lkml , Kees Cook , Andy Lutomirski , stgraber@ubuntu.com Subject: seccomp vs ptrace Message-ID: <20150318213007.GA24393@mail.hallyn.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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