From: Paul Moore <paul@paul-moore.com>
To: Roberto Sassu <roberto.sassu@huaweicloud.com>
Cc: linux-security-module@vger.kernel.org, Mimi Zohar <zohar@linux.ibm.com>
Subject: Re: [PATCH] lsm: drop LSM_ID_IMA
Date: Tue, 24 Oct 2023 17:15:26 -0400 [thread overview]
Message-ID: <CAHC9VhRayR7utthY8Bu4AbM33k4TA4Pbc57kZcYg955CwS7bQg@mail.gmail.com> (raw)
In-Reply-To: <72a92e27855af2291273209d328e1b79f3b61663.camel@huaweicloud.com>
On Thu, Oct 19, 2023 at 4:08 AM Roberto Sassu
<roberto.sassu@huaweicloud.com> wrote:
>
> On Wed, 2023-10-18 at 17:50 -0400, Paul Moore wrote:
> > When IMA becomes a proper LSM we will reintroduce an appropriate
> > LSM ID, but drop it from the userspace API for now in an effort
> > to put an end to debates around the naming of the LSM ID macro.
> >
> > Signed-off-by: Paul Moore <paul@paul-moore.com>
>
> Reviewed-by: Roberto Sassu <roberto.sassu@huawei.com>
Thanks. I just merged this into lsm/next-queue.
> This makes sense according to the new goal of making 'ima' and 'evm' as
> standalone LSMs.
>
> Otherwise, if we took existing LSMs, we should have defined
> LSM_ID_INTEGRITY, associated to DEFINE_LSM(integrity).
>
> If we proceed with the new direction, I will add the new LSM IDs as
> soon as IMA and EVM become LSMs.
Thank you.
--
paul-moore.com
next prev parent reply other threads:[~2023-10-24 21:15 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-18 21:50 [PATCH] lsm: drop LSM_ID_IMA Paul Moore
2023-10-19 8:08 ` Roberto Sassu
2023-10-20 21:56 ` Casey Schaufler
2023-10-23 15:20 ` Roberto Sassu
2023-10-23 15:48 ` Casey Schaufler
2023-10-23 16:11 ` Roberto Sassu
2023-10-24 13:18 ` Roberto Sassu
2023-10-24 21:18 ` Paul Moore
2023-10-25 10:35 ` Roberto Sassu
2023-10-25 13:14 ` Paul Moore
2023-10-25 14:06 ` Roberto Sassu
2023-10-25 14:36 ` Roberto Sassu
2023-10-26 2:54 ` Paul Moore
2023-10-26 8:49 ` Roberto Sassu
2023-10-26 2:43 ` Paul Moore
2023-10-25 16:46 ` Roberto Sassu
2023-10-24 21:15 ` Paul Moore [this message]
2023-11-13 4:05 ` Paul Moore
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=CAHC9VhRayR7utthY8Bu4AbM33k4TA4Pbc57kZcYg955CwS7bQg@mail.gmail.com \
--to=paul@paul-moore.com \
--cc=linux-security-module@vger.kernel.org \
--cc=roberto.sassu@huaweicloud.com \
--cc=zohar@linux.ibm.com \
/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).