From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751253AbdARXAa (ORCPT ); Wed, 18 Jan 2017 18:00:30 -0500 Received: from namei.org ([65.99.196.166]:33827 "EHLO namei.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750741AbdARXA3 (ORCPT ); Wed, 18 Jan 2017 18:00:29 -0500 Date: Thu, 19 Jan 2017 10:00:12 +1100 (AEDT) From: James Morris To: Kees Cook cc: Paul Moore , Casey Schaufler , LSM , John Johansen , Stephen Smalley , Tetsuo Handa , LKLM Subject: Re: [PATCH] LSM: Add /sys/kernel/security/lsm In-Reply-To: Message-ID: References: <6cfbf7e2-fe04-567b-2b33-7233763924a4@schaufler-ca.com> User-Agent: Alpine 2.20 (LRH 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 18 Jan 2017, Kees Cook wrote: > 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 > Casey: next time, please remember to include previous acks. -- James Morris