linux-kernel - Re: [PATCH v6 0/3] LSM: security module information improvements

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <7606f7b6-c4e0-4897-83bc-2b67abb55a2f@schaufler-ca.com>
Date:   Fri, 28 Oct 2016 08:22:09 -0700
From:   Casey Schaufler <casey@...aufler-ca.com>
To:     James Morris <jmorris@...ei.org>
Cc:     LSM <linux-security-module@...r.kernel.org>,
        John Johansen <john.johansen@...onical.com>,
        Paul Moore <paul@...l-moore.com>,
        Kees Cook <keescook@...omium.org>,
        Stephen Smalley <sds@...ho.nsa.gov>,
        Tetsuo Handa <penguin-kernel@...ove.sakura.ne.jp>,
        LKLM <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v6 0/3] LSM: security module information improvements

On 10/28/2016 2:28 AM, James Morris wrote:
> 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.

Fair enough. Development for the attr/context interface
in userspace can be done out of tree.

There is support for the other two patches, and I would
very much like to see them accepted.

>
> 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