From: James Morris <jmorris@namei.org>
To: Casey Schaufler <casey@schaufler-ca.com>
Cc: LSM <linux-security-module@vger.kernel.org>,
John Johansen <john.johansen@canonical.com>,
Paul Moore <paul@paul-moore.com>,
Kees Cook <keescook@chromium.org>,
Stephen Smalley <sds@tycho.nsa.gov>,
Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>,
LKLM <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v6 0/3] LSM: security module information improvements
Date: Fri, 28 Oct 2016 20:28:45 +1100 (AEDT) [thread overview]
Message-ID: <alpine.LRH.2.20.1610282023110.13327@namei.org> (raw)
In-Reply-To: <575cbfd2-e05b-83a9-faed-d07011c8bd5e@schaufler-ca.com>
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.
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
--
James Morris
<jmorris@namei.org>
next prev parent reply other threads:[~2016-10-28 9:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-26 23:56 Casey Schaufler
2016-10-27 0:01 ` [PATCH v6 1/3] LSM: Add /sys/kernel/security/lsm Casey Schaufler
2016-11-01 12:53 ` Tetsuo Handa
2016-11-01 17:25 ` Casey Schaufler
2016-11-04 14:11 ` Tetsuo Handa
2016-10-27 0:01 ` [PATCH v6 2/3] LSM: module hierarchy in /proc/.../attr Casey Schaufler
2016-10-27 0:01 ` [PATCH v6 3/3] LSM: Add context interface for proc attrs Casey Schaufler
2016-10-27 21:34 ` [PATCH v6 0/3] LSM: security module information improvements Kees Cook
2016-10-27 22:32 ` James Morris
2016-10-27 22:57 ` John Johansen
2016-10-28 0:05 ` Casey Schaufler
2016-10-28 9:28 ` James Morris [this message]
2016-10-28 15:22 ` 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=alpine.LRH.2.20.1610282023110.13327@namei.org \
--to=jmorris@namei.org \
--cc=casey@schaufler-ca.com \
--cc=john.johansen@canonical.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=sds@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 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®