From: "Guozihua (Scott)" <guozihua@huawei.com>
To: Mimi Zohar <zohar@linux.ibm.com>,
Roberto Sassu <roberto.sassu@huawei.com>,
Jonathan Corbet <corbet@lwn.net>
Cc: "linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
wangweiyang <wangweiyang2@huawei.com>,
Xiujianfeng <xiujianfeng@huawei.com>,
"linux-integrity@vger.kernel.org"
<linux-integrity@vger.kernel.org>
Subject: Re: [RESEND][PATCH] Documentation: added order requirement for ima_hash=
Date: Fri, 28 Jan 2022 17:32:04 +0800 [thread overview]
Message-ID: <aff671e4-6cff-d5d2-69c4-874ebd8bf54b@huawei.com> (raw)
In-Reply-To: <4626844528c5accb70a57870168091e002affb36.camel@linux.ibm.com>
On 2022/1/27 20:18, Mimi Zohar wrote:
> On Thu, 2022-01-27 at 14:35 +0800, Guozihua (Scott) wrote:
>
>>
>> I understand that the solution proposed here is to decommission template
>> "ima" and potentially removing related algo checks altogether?
>
> Eventually we might decide to do that, but right now we just want to
> address not being able to set "ima_template" after setting "ima_hash".
>
> thanks,
>
> Mimi
>
>
> .
Sure! I would come up with a solution.
--
Best
GUO Zihua
next prev parent reply other threads:[~2022-01-28 9:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-25 9:02 GUO Zihua
2022-01-26 0:14 ` Jonathan Corbet
2022-01-26 2:32 ` Guozihua (Scott)
2022-01-26 1:07 ` Mimi Zohar
2022-01-26 2:28 ` Guozihua (Scott)
2022-01-26 4:37 ` Mimi Zohar
2022-01-26 7:41 ` Guozihua (Scott)
2022-01-26 12:47 ` Mimi Zohar
2022-01-26 13:24 ` Roberto Sassu
2022-01-26 14:34 ` Mimi Zohar
2022-01-26 14:43 ` Roberto Sassu
2022-01-26 16:31 ` Jonathan Corbet
2022-01-27 6:35 ` Guozihua (Scott)
2022-01-27 12:18 ` Mimi Zohar
2022-01-28 9:32 ` Guozihua (Scott) [this message]
2022-01-28 10:24 ` Roberto Sassu
2022-01-28 14:33 ` Mimi Zohar
2022-01-28 16:01 ` Roberto Sassu
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=aff671e4-6cff-d5d2-69c4-874ebd8bf54b@huawei.com \
--to=guozihua@huawei.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=roberto.sassu@huawei.com \
--cc=wangweiyang2@huawei.com \
--cc=xiujianfeng@huawei.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
all inboxes | Powered by JetHome®