Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758067AbcJ1J25 (ORCPT ); Fri, 28 Oct 2016 05:28:57 -0400 Received: from [65.99.196.166] ([65.99.196.166]:58428 "EHLO namei.org" rhost-flags-FAIL-FAIL-OK-OK) by vger.kernel.org with ESMTP id S1755605AbcJ1J2y (ORCPT ); Fri, 28 Oct 2016 05:28:54 -0400 Date: Fri, 28 Oct 2016 20:28:45 +1100 (AEDT) From: James Morris To: Casey Schaufler cc: LSM , John Johansen , Paul Moore , Kees Cook , Stephen Smalley , Tetsuo Handa , LKLM Subject: Re: [PATCH v6 0/3] LSM: security module information improvements In-Reply-To: <575cbfd2-e05b-83a9-faed-d07011c8bd5e@schaufler-ca.com> Message-ID: References: <00f80c77-9623-7e9e-8980-63b362a4f16c@schaufler-ca.com> <575cbfd2-e05b-83a9-faed-d07011c8bd5e@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 Content-Length: 785 Lines: 21 On Thu, 27 Oct 2016, Casey Schaufler wrote: > The 3/3 patch is forward looking, I'll admit. Userspace > can start getting ready for the combined format in > advance of multiple major modules. When complete module > stacking patches are available I don't want to be addressing > "no userspace is set up to handle that" if at all possible. > I don't want to be Chicken or Egged to death. The attr/context > would be the ideal thing for the id command to report, as > the format would always be the same and identify the module(s). We do not add speculative infrastructure to the kernel. There is no consensus that we need major module stacking, and some of the technical issues (network secids, for example) are also as yet unresolved. - James -- James Morris