From: Song Liu <songliubraving@meta.com>
To: Casey Schaufler <casey@schaufler-ca.com>
Cc: Song Liu <songliubraving@meta.com>,
"roberto.sassu@huawei.com" <roberto.sassu@huawei.com>,
Paul Moore <paul@paul-moore.com>, Song Liu <song@kernel.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"linux-integrity@vger.kernel.org"
<linux-integrity@vger.kernel.org>,
"linux-security-module@vger.kernel.org"
<linux-security-module@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"dmitry.kasatkin@gmail.com" <dmitry.kasatkin@gmail.com>,
"eric.snowberg@oracle.com" <eric.snowberg@oracle.com>,
"jmorris@namei.org" <jmorris@namei.org>,
"serge@hallyn.com" <serge@hallyn.com>,
Kernel Team <kernel-team@meta.com>,
"brauner@kernel.org" <brauner@kernel.org>,
"jack@suse.cz" <jack@suse.cz>,
"viro@zeniv.linux.org.uk" <viro@zeniv.linux.org.uk>
Subject: Re: [RFC 0/2] ima: evm: Add kernel cmdline options to disable IMA/EVM
Date: Wed, 18 Dec 2024 16:48:46 +0000 [thread overview]
Message-ID: <746B14AA-7C89-451F-BE8D-3D2C485AA9E9@fb.com> (raw)
In-Reply-To: <518fdb73-8daf-4181-a8e6-528e4824d955@schaufler-ca.com>
> On Dec 18, 2024, at 8:42 AM, Casey Schaufler <casey@schaufler-ca.com> wrote:
>
> On 12/17/2024 10:41 PM, Song Liu wrote:
>>> On Dec 17, 2024, at 3:33 PM, Song Liu <songliubraving@meta.com> wrote:
>> [...]
>>
>>>>> +
>>>>> found = true;
>>>>> }
>>>>> }
>>>>> @@ -386,7 +389,7 @@ static void __init ordered_lsm_parse(const char *order, const char *origin)
>>>>>
>>>>> /* LSM_ORDER_LAST is always last. */
>>>>> for (lsm = __start_lsm_info; lsm < __end_lsm_info; lsm++) {
>>>>> - if (lsm->order == LSM_ORDER_LAST)
>>>>> + if (lsm->order == LSM_ORDER_LAST && is_enabled(lsm))
>>>>> append_ordered_lsm(lsm, " last");
>>> Before this change, lsm with order==LSM_ORDER_LAST is always considered
>>> enabled, which is a bug (if I understand you and Casey correctly).
>> According to commit 42994ee3cd7298b27698daa6848ed7168e72d056, LSMs with
>> order LSM_ORDER_LAST is expected to be always enabled:
>>
>> "Similarly to LSM_ORDER_FIRST, LSMs with LSM_ORDER_LAST are always enabled
>> and put at the end of the LSM list, if selected in the kernel
>> configuration. "
>>
>> Roberto, it feels weird to have two "last and always on" LSMs (ima and evm)
>> I guess this is not the expected behavior? At least, it appears to be a
>> surprise for Paul and Casey.
>
> I can't speak for Paul, but having multiple "first" and "last" entries
> comes as no surprise to me. We should probably have used LSM_ORDER_EARLY
> and LSM_ORDER_LATE instead of LSM_ORDER_FIRST and LSM_ORDER_LAST. As for
> "always on", I recall that being an artifact of compatibility for the
> security= boot option.
Yes, _LATE makes more sense than _LAST. _LAST is a bit weird, but not
surprising.
By "surprise to you and Paul", I meant the "always on" part. It appears
to me that both you and Paul believed that ima and evm are only enabled
with proper lsm= cmdline. Or maybe I totally misunderstood your
comments?
Thanks,
Song
next prev parent reply other threads:[~2024-12-18 16:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-17 20:25 Song Liu
2024-12-17 20:25 ` [RFC 1/2] ima: Add kernel parameter to disable IMA Song Liu
2024-12-17 20:25 ` [RFC 2/2] evm: Add kernel parameter to disable EVM Song Liu
2024-12-17 21:29 ` [RFC 0/2] ima: evm: Add kernel cmdline options to disable IMA/EVM Casey Schaufler
2024-12-17 21:59 ` Paul Moore
2024-12-17 22:04 ` Song Liu
2024-12-17 22:47 ` Song Liu
2024-12-17 23:16 ` Paul Moore
2024-12-17 23:33 ` Song Liu
2024-12-18 6:41 ` Song Liu
2024-12-18 16:42 ` Casey Schaufler
2024-12-18 16:48 ` Song Liu [this message]
2024-12-17 22:02 ` Song Liu
2024-12-18 11:02 ` Mimi Zohar
2024-12-18 17:07 ` Song Liu
2024-12-19 15:40 ` Roberto Sassu
2024-12-19 17:46 ` Song Liu
2024-12-19 18:18 ` Mimi Zohar
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=746B14AA-7C89-451F-BE8D-3D2C485AA9E9@fb.com \
--to=songliubraving@meta.com \
--cc=brauner@kernel.org \
--cc=casey@schaufler-ca.com \
--cc=dmitry.kasatkin@gmail.com \
--cc=eric.snowberg@oracle.com \
--cc=jack@suse.cz \
--cc=jmorris@namei.org \
--cc=kernel-team@meta.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=roberto.sassu@huawei.com \
--cc=serge@hallyn.com \
--cc=song@kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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®