[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHC9VhRQ7xpeSX7b3VZfzQ15noJ8mgauNMuHWo_n3hMgsYMAfQ@mail.gmail.com>
Date: Mon, 16 Oct 2023 11:06:33 -0400
From: Paul Moore <paul@...l-moore.com>
To: Roberto Sassu <roberto.sassu@...weicloud.com>
Cc: Casey Schaufler <casey@...aufler-ca.com>,
linux-security-module@...r.kernel.org, jmorris@...ei.org,
serge@...lyn.com, keescook@...omium.org,
john.johansen@...onical.com, penguin-kernel@...ove.sakura.ne.jp,
stephen.smalley.work@...il.com, linux-kernel@...r.kernel.org,
linux-api@...r.kernel.org, mic@...ikod.net
Subject: Re: [PATCH v15 00/11] LSM: Three basic syscalls
On Mon, Oct 16, 2023 at 8:05 AM Roberto Sassu
<roberto.sassu@...weicloud.com> wrote:
>
> Sorry, I just noticed LSM_ID_IMA. Since we have the 'integrity' LSM, I
> think it should be LSM_ID_INTEGRITY.
>
> Mimi, all, do you agree? If yes, I send a patch shortly.
I believe LSM_ID_IMA is the better option, despite "integrity" already
being present in Kconfig and possibly other areas. "IMA" is a
specific thing/LSM whereas "integrity" is a property, principle, or
quality. Especially as we move forward with promoting IMA as a full
and proper LSM, we should work towards referring to it as "IMA" and
not "integrity".
If anything we should be working to support "IMA" in places where we
currently have "integrity" so that we can eventually deprecate
"integrity".
--
paul-moore.com
Powered by blists - more mailing lists