linux-kernel - Re: [PATCH] procfs: add smack subdir to attrs

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: <76f4dd96-76ca-a7ec-313a-b8ab72b0181f@schaufler-ca.com>
Date:   Thu, 1 Jun 2017 16:59:24 -0700
From:   Casey Schaufler <casey@...aufler-ca.com>
To:     James Morris <jmorris@...ei.org>
Cc:     LKLM <linux-kernel@...r.kernel.org>,
        LSM <linux-security-module@...r.kernel.org>
Subject: Re: [PATCH] procfs: add smack subdir to attrs

On 6/1/2017 4:38 PM, James Morris wrote:
> On Thu, 1 Jun 2017, Casey Schaufler wrote:
>
>> Subject: [PATCH] procfs: add smack subdir to attrs
> Is there value in this without major stacking support?

Yes. If a Smack aware application reads /proc/self/attr/current
it has no way to know if what it sees is a Smack label or an
SELinux context. True, the application can look elsewhere
(i.e. /sys/kernel/security/lsm) to find out which is enabled.
But the real fix is for Smack to use a different interface
than SELinux. Which is what this does. True, it will be even
more important when/if major stacking comes in, but it is still
significant now, and I would like to have it regardless of
the future acceptance of major stacking.