From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751530AbdARXaI (ORCPT ); Wed, 18 Jan 2017 18:30:08 -0500 Received: from namei.org ([65.99.196.166]:33834 "EHLO namei.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751350AbdARXaE (ORCPT ); Wed, 18 Jan 2017 18:30:04 -0500 Date: Thu, 19 Jan 2017 10:29:36 +1100 (AEDT) From: James Morris To: Casey Schaufler cc: LSM , John Johansen , Paul Moore , Kees Cook , Stephen Smalley , Tetsuo Handa , LKLM Subject: Re: [PATCH] LSM: Add /sys/kernel/security/lsm In-Reply-To: <6cfbf7e2-fe04-567b-2b33-7233763924a4@schaufler-ca.com> 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 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. > This doesn't apply cleanly to my tree. -- James Morris