From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753066AbdBPDPN (ORCPT ); Wed, 15 Feb 2017 22:15:13 -0500 Received: from mail-vk0-f52.google.com ([209.85.213.52]:36674 "EHLO mail-vk0-f52.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752597AbdBPDPM (ORCPT ); Wed, 15 Feb 2017 22:15:12 -0500 MIME-Version: 1.0 In-Reply-To: <1487043928-5982-2-git-send-email-tyhicks@canonical.com> References: <1487043928-5982-1-git-send-email-tyhicks@canonical.com> <1487043928-5982-2-git-send-email-tyhicks@canonical.com> From: Andy Lutomirski Date: Wed, 15 Feb 2017 19:14:50 -0800 Message-ID: Subject: Re: [PATCH v3 1/4] seccomp: Add sysctl to display available actions To: Tyler Hicks Cc: Paul Moore , Eric Paris , Kees Cook , Will Drewry , linux-audit@redhat.com, "linux-kernel@vger.kernel.org" , John Crispin , linux-api@ver.kernel.org Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Feb 13, 2017 at 7:45 PM, Tyler Hicks wrote: > This patch creates a read-only sysctl containing an ordered list of > seccomp actions that the kernel supports. The ordering, from left to > right, is the lowest action value (kill) to the highest action value > (allow). Currently, a read of the sysctl file would return "kill trap > errno trace allow". The contents of this sysctl file can be useful for > userspace code as well as the system administrator. Would this make more sense as a new seccomp(2) mode a la SECCOMP_HAS_ACTION? Then sandboxy things that have no fs access could use it. --Andy