From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753424AbdARVHz (ORCPT ); Wed, 18 Jan 2017 16:07:55 -0500 Received: from mail-io0-f174.google.com ([209.85.223.174]:36028 "EHLO mail-io0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753278AbdARVHw (ORCPT ); Wed, 18 Jan 2017 16:07:52 -0500 MIME-Version: 1.0 In-Reply-To: References: <6cfbf7e2-fe04-567b-2b33-7233763924a4@schaufler-ca.com> From: Kees Cook Date: Wed, 18 Jan 2017 13:01:27 -0800 X-Google-Sender-Auth: CNWH42PJ-F0pwKcre5GSdv_Ejsc Message-ID: Subject: Re: [PATCH] LSM: Add /sys/kernel/security/lsm To: Paul Moore Cc: James Morris , Casey Schaufler , LSM , John Johansen , Stephen Smalley , Tetsuo Handa , LKLM 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 Wed, Jan 18, 2017 at 11:22 AM, Paul Moore wrote: > On Wed, Jan 18, 2017 at 7:43 AM, James Morris wrote: >> On Tue, 17 Jan 2017, Casey Schaufler wrote: >> >>> Subject: [PATCH] LSM: Add /sys/kernel/security/lsm >>> >>> I am still tired of having to find indirect ways to determine >>> what security modules are active on a system. I have added >>> /sys/kernel/security/lsm, which contains a comma separated >>> list of the active secuirty modules. No more groping around >>> in /proc/filesystems or other clever hacks. >>> >>> Unchanged from previous versions except for being updated >>> to the latest security next branch. >>> >> >> Any objections to merging this? >> > > I'm fairly certain I ack'd a prior version of this at one point ... > > Acked-by: Paul Moore Yeah, me too. Acked-by: Kees Cook -Kees -- Kees Cook Nexus Security