From: Casey Schaufler <casey@schaufler-ca.com>
To: Eric Paris <eparis@redhat.com>
Cc: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>,
jmorris@namei.org, linux-security-module@vger.kernel.org,
selinux@tycho.nsa.gov, john.johansen@canonical.com,
keescook@chromium.org, Casey Schaufler <casey@schaufler-ca.com>
Subject: Re: [PATCH v10] LSM: Multiple concurrent LSMs
Date: Wed, 12 Dec 2012 08:24:49 -0800 [thread overview]
Message-ID: <50C8AFD1.1070905@schaufler-ca.com> (raw)
In-Reply-To: <1355327754.3527.37.camel@localhost>
On 12/12/2012 7:55 AM, Eric Paris wrote:
> On Wed, 2012-12-12 at 07:48 -0800, Casey Schaufler wrote:
>
> How about asking every LSM to implement a new 'enable' function. If the
> LSM is not 'present' only the new 'enable' function can be used. If the
> LSM is present either the legacy enable function every LSM uses today or
> the new enable function can be used. Thus even if you build the kernel
> with stacking, you cannot enable a non-present LSM unless the tools have
> been updated.
I'm sorry, but I am having trouble understanding what you're suggesting.
>
> I'd envision for SELinux it would mean that we would disable/not
> expose/whatever /sys/fs/selinux/load when SELinux was not present. And
> we'd have a new /sys/fs/selinux/new_load which could be used in its
> place.
>
> Thoughts?
>
> -Eric
>
>
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next prev parent reply other threads:[~2012-12-12 16:24 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <50C65DE2.5090909@schaufler-ca.com>
[not found] ` <201212112128.ADI26010.OQJVLOFSOFtHMF@I-love.SAKURA.ne.jp>
2012-12-11 15:31 ` [PATCH v10] LSM: Multiple concurrent LSMs Casey Schaufler
[not found] ` <201212122159.CEC09839.HMOFtQFLJSVFOO@I-love.SAKURA.ne.jp>
2012-12-12 15:48 ` Casey Schaufler
2012-12-12 15:55 ` Eric Paris
2012-12-12 16:24 ` Casey Schaufler [this message]
2012-12-12 16:33 ` Eric Paris
2012-12-12 17:04 ` Casey Schaufler
2012-12-12 17:11 ` Eric Paris
[not found] ` <CAGXu5jLf+apZK5poD6GKzLkC+p6+mAqKhU3neoOZjr2JumvmpA@mail.gmail.com>
2012-12-12 17:22 ` Eric Paris
2012-12-12 17:31 ` Casey Schaufler
2012-12-12 17:47 ` Eric Paris
2012-12-12 18:25 ` Casey Schaufler
2012-12-12 18:47 ` Eric Paris
2012-12-12 20:46 ` Casey Schaufler
2012-12-12 20:51 ` Eric Paris
2012-12-12 22:01 ` Casey Schaufler
[not found] ` <201212132106.AFI82338.QMFHFLSJOtOOFV@I-love.SAKURA.ne.jp>
2012-12-13 16:12 ` Eric Paris
2012-12-13 16:31 ` Casey Schaufler
[not found] ` <CAGXu5jJf4NEvs6TjVCBxgd9e8cGwag_-viEntgTBUq85fULr8w@mail.gmail.com>
2012-12-16 3:06 ` Casey Schaufler
[not found] ` <201212142326.DDG90674.SFHFMOOVLFJtQO@I-love.SAKURA.ne.jp>
2012-12-14 15:07 ` Eric Paris
2012-12-13 16:38 ` Casey Schaufler
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=50C8AFD1.1070905@schaufler-ca.com \
--to=casey@schaufler-ca.com \
--cc=eparis@redhat.com \
--cc=jmorris@namei.org \
--cc=john.johansen@canonical.com \
--cc=keescook@chromium.org \
--cc=linux-security-module@vger.kernel.org \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=selinux@tycho.nsa.gov \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.