From: David Laight <David.Laight@ACULAB.COM>
To: 'Chris von Recklinghausen' <crecklin@redhat.com>,
"ardb@kernel.org" <ardb@kernel.org>,
"simo@redhat.com" <simo@redhat.com>,
"rafael@kernel.org" <rafael@kernel.org>,
"decui@microsoft.com" <decui@microsoft.com>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH v4 1/1] use crc32 instead of md5 for hibernation e820 integrity check
Date: Fri, 9 Apr 2021 16:56:05 +0000 [thread overview]
Message-ID: <6be63531313d46caa7161697bf240dfc@AcuMS.aculab.com> (raw)
In-Reply-To: <20210408104629.31357-1-crecklin@redhat.com>
From: Chris von Recklinghausen
> Sent: 08 April 2021 11:46
>
> Suspend fails on a system in fips mode because md5 is used for the e820
> integrity check and is not available. Use crc32 instead.
>
> Prior to this patch, MD5 is used only to create a digest to ensure integrity of
> the region, no actual encryption is done. This patch set changes the integrity
> check to use crc32 instead of md5 since crc32 is available in both FIPS and
> non-FIPS modes.
>
> Note that the digest is only used as an integrity check. No actual encryption
> is done.
If crc32 is good enough, would a 1's compliment sum be good enough?
It is likely to be faster to calculate and not need special
functions be built into the kernel at all.
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
next prev parent reply other threads:[~2021-04-09 16:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-08 10:46 [PATCH v4 1/1] use crc32 instead of md5 for hibernation e820 integrity check Chris von Recklinghausen
2021-04-08 13:01 ` Simo Sorce
2021-04-09 16:56 ` David Laight [this message]
2021-04-09 19:28 ` Chris von Recklinghausen
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=6be63531313d46caa7161697bf240dfc@AcuMS.aculab.com \
--to=david.laight@aculab.com \
--cc=ardb@kernel.org \
--cc=crecklin@redhat.com \
--cc=decui@microsoft.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=simo@redhat.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