From: GUO Zihua <guozihua@huawei.com>
To: <corbet@lwn.net>, <zohar@linux.ibm.com>
Cc: <linux-doc@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<roberto.sassu@huawei.com>, <wangweiyang2@huawei.com>,
<xiujianfeng@huawei.com>, <linux-integrity@vger.kernel.org>,
<guozihua@huawei.com>
Subject: [RESEND][PATCH] Documentation: added order requirement for ima_hash=
Date: Tue, 25 Jan 2022 17:02:37 +0800 [thread overview]
Message-ID: <20220125090237.120357-1-guozihua@huawei.com> (raw)
From: Guo Zihua <guozihua@huawei.com>
Commandline parameter ima_hash= and ima_template= has order requirement
for them to work correctly together. Namely ima_hash= must be
specified after ima_template=, otherwise ima_template= will be ignored.
The reason is that when handling ima_hash=, ima template would be set to
the default value if it has not been initialized already, and that value
cannot be changed afterwards by ima_template=.
This patch adds this limitation to the documentation.
Reviewed-by: Roberto Sassu <roberto.sassu@huawei.com>
Signed-off-by: Guo Zihua <guozihua@huawei.com>
---
Documentation/admin-guide/kernel-parameters.txt | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/Documentation/admin-guide/kernel-parameters.txt b/Documentation/admin-guide/kernel-parameters.txt
index f5a27f067db9..1b5aa6ca65f8 100644
--- a/Documentation/admin-guide/kernel-parameters.txt
+++ b/Documentation/admin-guide/kernel-parameters.txt
@@ -1843,6 +1843,10 @@
The list of supported hash algorithms is defined
in crypto/hash_info.h.
+ This parameter must be specified after ima_template=,
+ as it would set the default template and that cannot be
+ changed by ima_template= afterwards.
+
ima_policy= [IMA]
The builtin policies to load during IMA setup.
Format: "tcb | appraise_tcb | secure_boot |
@@ -1879,6 +1883,9 @@
Formats: { "ima" | "ima-ng" | "ima-sig" }
Default: "ima-ng"
+ This parameter must be specified before ima_hash=.
+ Please refer to ima_hash= for further explanation.
+
ima_template_fmt=
[IMA] Define a custom template format.
Format: { "field1|...|fieldN" }
--
2.17.1
next reply other threads:[~2022-01-25 9:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-25 9:02 GUO Zihua [this message]
2022-01-26 0:14 ` [RESEND][PATCH] Documentation: added order requirement for ima_hash= 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)
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=20220125090237.120357-1-guozihua@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;
as well as URLs for NNTP newsgroup(s).