From: Jonathan McDowell <noodles@earth.li>
To: Mimi Zohar <zohar@linux.ibm.com>
Cc: linux-integrity@vger.kernel.org, Stefan Berger <stefanb@linux.ibm.com>
Subject: Re: [PATCH] ima: fix violation measurement list record
Date: Fri, 1 Jul 2022 23:41:49 +0100 [thread overview]
Message-ID: <Yr94LQGboFv4f1xG@earth.li> (raw)
In-Reply-To: <20220701201325.396766-1-zohar@linux.ibm.com>
On Fri, Jul 01, 2022 at 04:13:25PM -0400, Mimi Zohar wrote:
> Although the violation digest in the IMA measurement list is always
> zeroes, the size of the digest should be based on the hash algorithm.
> Until recently the hash algorithm was hard coded to sha1. Fix the
> violation digest size included in the IMA measurement list.
>
> This is just a cosmetic which should not affect attestation.
>
> Reported-by: Stefan Berger <stefanb@linux.ibm.com>
> Fixes: 09091c44cb73 ("ima: use IMA default hash algorithm for integrity violations")
> Signed-off-by: Mimi Zohar <zohar@linux.ibm.com>
> ---
> security/integrity/ima/ima_template_lib.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/security/integrity/ima/ima_template_lib.c b/security/integrity/ima/ima_template_lib.c
> index c877f01a5471..67359845c975 100644
> --- a/security/integrity/ima/ima_template_lib.c
> +++ b/security/integrity/ima/ima_template_lib.c
> @@ -326,7 +326,7 @@ static int ima_eventdigest_init_common(const u8 *digest, u32 digestsize,
> * Make room for the digest by increasing the offset of
> * IMA_DIGEST_SIZE.
> */
> - offset += IMA_DIGEST_SIZE;
> + offset += hash_digest_size[hash_algo];
Update the comment as well?
> return ima_write_template_field_data(buffer, offset + digestsize,
> fmt, field_data);
> --
> 2.27.0
>
J.
--
This isn't an office. It's Hell with fluorescent lighting.
next prev parent reply other threads:[~2022-07-01 23:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-01 20:13 [PATCH] ima: fix violation measurement list record Mimi Zohar
2022-07-01 22:41 ` Jonathan McDowell [this message]
2022-07-01 22:43 ` 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=Yr94LQGboFv4f1xG@earth.li \
--to=noodles@earth.li \
--cc=linux-integrity@vger.kernel.org \
--cc=stefanb@linux.ibm.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