linux-kernel - Re: [PATCH] LSM: Add /sys/kernel/security/lsm

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] [day] [month] [year] [list]

Date:   Wed, 18 Jan 2017 15:52:42 -0800
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>,
        Casey Schaufler <casey@...aufler-ca.com>
Subject: Re: [PATCH] LSM: Add /sys/kernel/security/lsm

On 1/18/2017 3:29 PM, 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.
>>
> This doesn't apply cleanly to my tree.

The AppArmor changes that you've added since you pulled
rc3 introduced some offset issues. Should I update my patch
to reflect them, or do you want to resolve the conflict?
I don't much care either way. Just let me know.