From: "Stephan Müller" <smueller@chronox.de>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: linux-crypto@vger.kernel.org, Niolai Stange <nstange@suse.com>,
Simo Sorce <simo@redhat.com>
Subject: [PATCH v2 0/2] crypto: HMAC - disallow keys < 112 bits in FIPS mode
Date: Tue, 01 Feb 2022 09:40:24 +0100 [thread overview]
Message-ID: <4609802.vXUDI8C0e8@positron.chronox.de> (raw)
In-Reply-To: <YfN1HKqL9GT9R25Z@gondor.apana.org.au>
Hi,
this is patch set version 2 for adding the HMAC limitation to disallow
keys < 112 bits in FIPS mode.
Version 2 changes:
As requested, instead of ifdef'ing test vectors out that violate the
constraint added with this patch set, they are compiled but disabled in
FIPS mode based on the .fips_skip flag.
The first patch adds the generic support for the fips_skip flag to
hashes / HMAC test vectors similarly to the support found for symmetric
algorithms.
The second patch uses the fips_skip flag to mark offending test vectors.
Stephan Mueller (2):
crypto: HMAC - add fips_skip support
crypto: HMAC - disallow keys < 112 bits in FIPS mode
crypto/hmac.c | 4 ++++
crypto/testmgr.c | 3 +++
crypto/testmgr.h | 11 +++++++++++
3 files changed, 18 insertions(+)
--
2.33.1
next prev parent reply other threads:[~2022-02-01 8:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-07 19:25 [PATCH] crypto: HMAC - disallow keys < 112 bits in FIPS mode Stephan Müller
2022-01-07 23:28 ` Eric Biggers
2022-01-08 6:39 ` Stephan Müller
2022-01-11 7:17 ` Stephan Mueller
2022-01-28 4:46 ` Herbert Xu
2022-01-28 6:05 ` Stephan Mueller
2022-02-01 8:40 ` Stephan Müller [this message]
2022-02-01 8:40 ` [PATCH v2 1/2] crypto: HMAC - add fips_skip support Stephan Müller
2022-02-01 8:41 ` [PATCH v2 2/2] crypto: HMAC - disallow keys < 112 bits in FIPS mode Stephan Müller
2022-02-11 9:34 ` [PATCH v2 0/2] " Herbert Xu
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=4609802.vXUDI8C0e8@positron.chronox.de \
--to=smueller@chronox.de \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=nstange@suse.com \
--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