From: Casey Schaufler <casey@schaufler-ca.com>
To: "José Bollo" <jobol@nonadev.net>
Cc: James Morris <jmorris@namei.org>,
LKLM <linux-kernel@vger.kernel.org>,
LSM <linux-security-module@vger.kernel.org>
Subject: Re: [PATCH] procfs: add smack subdir to attrs
Date: Tue, 6 Jun 2017 07:45:28 -0700 [thread overview]
Message-ID: <a79fbe99-20c7-8265-9d7e-d6f0c9490813@schaufler-ca.com> (raw)
In-Reply-To: <20170606135815.0b6372de@d-jobol.iot.bzh>
On 6/6/2017 4:58 AM, José Bollo wrote:
> On Thu, 1 Jun 2017 16:59:24 -0700
> Casey Schaufler <casey@schaufler-ca.com> wrote:
>
>> 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.
> I agree that it is a nice forward movement to leave the mud.
>
> I have a subsidiary question to ask. Should we keep the name 'attr' for
> the subdirectory? It seems at least convenient but if a better name is
> valuable (security, lsm, ...) why not to switch now?
Too many things would break. It's really a matter of taste in any case.
>
> BR josé
>
>> --
>> To unsubscribe from this list: send the line "unsubscribe
>> linux-security-module" in the body of a message to
>> majordomo@vger.kernel.org More majordomo info at
>> http://vger.kernel.org/majordomo-info.html
>
prev parent reply other threads:[~2017-06-06 14:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-01 19:49 Casey Schaufler
2017-06-01 23:38 ` James Morris
2017-06-01 23:59 ` Casey Schaufler
2017-06-06 11:58 ` José Bollo
2017-06-06 14:45 ` Casey Schaufler [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a79fbe99-20c7-8265-9d7e-d6f0c9490813@schaufler-ca.com \
--to=casey@schaufler-ca.com \
--cc=jmorris@namei.org \
--cc=jobol@nonadev.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®