From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933762AbdABR1e (ORCPT ); Mon, 2 Jan 2017 12:27:34 -0500 Received: from youngberry.canonical.com ([91.189.89.112]:52857 "EHLO youngberry.canonical.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933003AbdABR1T (ORCPT ); Mon, 2 Jan 2017 12:27:19 -0500 From: Tyler Hicks To: Paul Moore , Eric Paris , Kees Cook , Andy Lutomirski , Will Drewry Cc: linux-audit@redhat.com, linux-kernel@vger.kernel.org Subject: [PATCH 0/2] Support auditing while still allowing a syscall Date: Mon, 2 Jan 2017 17:26:37 +0000 Message-Id: <1483377999-15019-1-git-send-email-tyhicks@canonical.com> X-Mailer: git-send-email 2.7.4 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Allow application authors to opt into auditing a syscall before allowing it. This differs slightly from SECCOMP_RET_ALLOW in that an audit message is generated for the syscall. It can be useful when initially setting up a seccomp sandbox for your application if you set the default action to audit instead of, for example, kill when the application makes a restricted system call. The application author can easily compile a list of syscalls that need to be allowed instead of iteratively building the application, testing the application, updating the filter, and repeating until all appropriate system calls have been allowed. This patch set depends on the following patch set: https://lkml.kernel.org/r/1483375990-14948-1-git-send-email-tyhicks@canonical.com (At least, I hope it shows up at that link soon because marc.info doesn't yet know of the message-id.) The corresponding libseccomp changes can be found here: https://github.com/seccomp/libseccomp/pull/64 Thanks! Tyler