From: Paul Moore <paul@paul-moore.com>
To: Casey Schaufler <casey@schaufler-ca.com>,
Edwin Zimmerman <edwin@211mainstreet.net>
Cc: LSM <linux-security-module@vger.kernel.org>
Subject: Re: New LSM hooks
Date: Tue, 5 Feb 2019 14:58:35 -0500 [thread overview]
Message-ID: <CAHC9VhSdktacjbxSXA1k9Hqj-NpJca50UtE-9Ado-R9mB35j7g@mail.gmail.com> (raw)
In-Reply-To: <c15e8f04-df2e-40f4-d227-754d03de3dd0@schaufler-ca.com>
On Tue, Feb 5, 2019 at 2:26 PM Casey Schaufler <casey@schaufler-ca.com> wrote:
> On 2/5/2019 10:28 AM, Edwin Zimmerman wrote:
> > Here's my suggestion for starters. According to kernel documentation, new
> > LSMs must be documented before being accepted. Perhaps we need a
> > similar requirement for LSM hooks.
>
> That would be handy. The documentation would need to cover
> the purpose for the hook and how a security module would be
> expected to use it.
We have a weak version of this now with the comments in
include/linux/lsm_hooks.h, and as far as I recall we've pushed back on
people who have changed the hooks without some documentation in the
comments. Whatever we end up doing, let's try to keep this going as a
practice.
--
paul moore
www.paul-moore.com
next prev parent reply other threads:[~2019-02-05 19:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-05 17:40 New LSM hooks Casey Schaufler
2019-02-05 18:15 ` Paul Moore
2019-02-05 20:04 ` Casey Schaufler
2019-02-06 0:01 ` Paul Moore
2019-02-06 1:11 ` James Morris
2019-02-06 13:20 ` Stephen Smalley
2019-02-06 17:24 ` Casey Schaufler
2019-02-06 17:44 ` Stephen Smalley
2019-02-06 18:18 ` Casey Schaufler
2019-02-06 16:30 ` Casey Schaufler
2019-02-06 17:06 ` Stephen Smalley
2019-02-06 17:44 ` Casey Schaufler
2019-02-06 17:48 ` Stephen Smalley
2019-02-05 18:28 ` Edwin Zimmerman
2019-02-05 19:25 ` Casey Schaufler
2019-02-05 19:58 ` Paul Moore [this message]
2019-02-05 20:10 ` Edwin Zimmerman
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=CAHC9VhSdktacjbxSXA1k9Hqj-NpJca50UtE-9Ado-R9mB35j7g@mail.gmail.com \
--to=paul@paul-moore.com \
--cc=casey@schaufler-ca.com \
--cc=edwin@211mainstreet.net \
--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;
as well as URLs for NNTP newsgroup(s).