n-cryptographic checksum such as CRC-32 is sufficient to detect such
> inadvertent deviations.
>
> Fixes: 62a03defeabd ("PM / hibernate: Verify the consistent of e820 memory
> map
>by md5 digest")
>
> Signed-off-by: Chris von Recklinghausen
> ---
Test
> From: Chris von Recklinghausen
> Sent: Thursday, April 1, 2021 9:42 AM
> To: a...@kernel.org; s...@redhat.com; raf...@kernel.org; Dexuan Cui
> ; linux...@vger.kernel.org;
> linux-crypto@vger.kernel.org; linux-ker...@vger.kernel.org
> Subject: [PATCH v2 1/1] use crc32
> From: Eric Biggers
> Sent: Monday, March 29, 2021 6:26 PM
> ...
> It looks like your userspace is using tcrypt.ko to request that the kernel
> test
> "ofb(aes)", but your kernel doesn't have CONFIG_CRYPTO_OFB enabled so the
> test fails as expected.
Hi Eric,
Thanks for the explanation! Yes,
Hi,
MD5 was marked incompliant with FIPS in 2009:
a3bef3a31a19 ("crypto: testmgr - Skip algs not flagged fips_allowed in fips
mode")
a1915d51e8e7 ("crypto: testmgr - Mark algs allowed in fips mode")
But hibernation_e820_save() is still using MD5, and fails in FIPS mode
due to the 2018 patch:
749f
Hi all,
The v5.12.0-rc5 kernel (1e43c377a79f) panics with fips=1.
Please refer to the below panic call-trace. The kernel config file and
the full kernel messages are also attached.
Is this a known issue?
Thanks,
-- Dexuan
Starting dracut pre-udev hook...
[7.260424] alg: self-tests
