From: Mimi Zohar <zohar@linux.ibm.com>
To: Enrico Bravi <enrico.bravi@polito.it>,
linux-integrity@vger.kernel.org, roberto.sassu@huawei.com
Cc: Silvia Sisinni <silvia.sisinni@polito.it>
Subject: Re: [RFC][PATCH] ima: add crypto agility support for template-hash algorithm
Date: Tue, 19 Dec 2023 15:54:03 -0500 [thread overview]
Message-ID: <8bf7eaf170cf609fb4280475d3340179283fd196.camel@linux.ibm.com> (raw)
In-Reply-To: <20231214145152.36985-1-enrico.bravi@polito.it>
Hi Enrico,
On Thu, 2023-12-14 at 15:51 +0100, Enrico Bravi wrote:
> The purpose of this patch is to add the possibility to configure the hash
> algorithm to use when calculating the template-hash.
The patch description should be written in the imperative mood. For an
explanation, please refer to "Describe your changes" in
Documentation/process/submitting-patches.rst.
For example:
The second field of the IMA measurement list, the template data hash,
contains a fixed sized SHA1 digest. Add support to replace the SHA1
digest with other hash algorithms. For backwards compatability, only
the new larger digests will be prefixed with ...
> The ima_template_hash command line parameter has been introduced to enable
> this configuration.
The term "ima_template_hash" could be misconstrued to refer to the hash
algorithm used to calculate the file digest. To differentiate between
the hash algorithm used to calculate the file digest, the term
'ima_template_data_hash' is longer, but I think clearer.
> The entry will contain the hash_algo_name before the actual template-hash,
> separated by a colon (:).
This chnage will break existing userspace applications, unless the SHA1
digest isn't prefixed.
> An example of the resulting ima log is the following:
>
> 10 sha256:64326[...]25313 ima-ng sha1:5fc9b[...]974e6 boot_aggregate
> 10 sha256:afd64[...]e3123 ima-ng sha1:5a493[...]f9566 /init
> 10 sha256:99329[...]a6353 ima-ng sha1:8c87d[...]3d8c7 /usr/bin/sh
> 10 sha256:a16ad[...]2ac0e ima-ng sha1:59d4b[...]330b0 /etc/ld.so.cache
>
> This patch has been created starting from the master branch of the main tree:
> <git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git>
With the base-commit included at the end of the cover letter, this
comment is unnessary. Please remove.
thanks,
Mimi
>
> Signed-off-by: Silvia Sisinni <silvia.sisinni@polito.it>
> Signed-off-by: Enrico Bravi <enrico.bravi@polito.it>
next prev parent reply other threads:[~2023-12-19 20:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-14 14:51 [RFC][PATCH] ima: add crypto agility support for template-hash algorithm Enrico Bravi
2023-12-19 20:54 ` Mimi Zohar [this message]
2023-12-21 14:38 ` Enrico Bravi
2023-12-21 22:05 ` Mimi Zohar
2023-12-25 13:00 ` Guozihua (Scott)
2023-12-26 15:36 ` Ken Goldman
2023-12-27 14:03 ` Mimi Zohar
2024-01-09 17:05 ` Silvia Sisinni
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=8bf7eaf170cf609fb4280475d3340179283fd196.camel@linux.ibm.com \
--to=zohar@linux.ibm.com \
--cc=enrico.bravi@polito.it \
--cc=linux-integrity@vger.kernel.org \
--cc=roberto.sassu@huawei.com \
--cc=silvia.sisinni@polito.it \
/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