From: Vladis Dronov <vdronov@redhat.com>
To: Herbert Xu <herbert@gondor.apana.org.au>,
"David S . Miller" <davem@davemloft.net>
Cc: Nicolai Stange <nstange@suse.de>,
Elliott Robert <elliott@hpe.com>,
Stephan Mueller <smueller@chronox.de>,
Eric Biggers <ebiggers@google.com>,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
Vladis Dronov <vdronov@redhat.com>
Subject: [PATCH v2 0/6] Trivial set of FIPS 140-3 related changes
Date: Thu, 29 Dec 2022 21:37:02 +0100 [thread overview]
Message-ID: <20221229203708.13628-1-vdronov@redhat.com> (raw)
Hi,
This patchset and cover letter was initially composed by Nicolai Stange
and sent earlier as:
https://lore.kernel.org/r/20221108142025.13461-1-nstange@suse.de/
with a subject: [PATCH 0/4] Trivial set of FIPS 140-3 related changes
I'm adding patches 2 and 3 which (I hope) resolve issues spotted by
reviewers of previous version of the patchset. This new patchset should
ease our future kernel work on the FIPS mode.
I'm quoting Nicolai's cover letter here:
> Hi all,
>
> these four rather unrelated patches are basically a dump of some of the
> more trivial changes required for working towards FIPS 140-3 conformance.
>
> Please pick as you deem appropriate.
>
> Thanks!
>
> Nicolai
v2:
- fixed a block comment formatting
- "Reviewed-by: Eric Biggers" was copied from the v1 thread:
https://lore.kernel.org/r/Y6OXuT95MlkNanSR@sol.localdomain/
Nicolai Stange (4):
crypto: xts - restrict key lengths to approved values in FIPS mode
crypto: testmgr - disallow plain cbcmac(aes) in FIPS mode
crypto: testmgr - disallow plain ghash in FIPS mode
crypto: testmgr - allow ecdsa-nist-p256 and -p384 in FIPS mode
Vladis Dronov (2):
crypto: xts - drop xts_check_key()
crypto: xts - drop redundant xts key check
arch/s390/crypto/aes_s390.c | 4 ---
arch/s390/crypto/paes_s390.c | 2 +-
crypto/testmgr.c | 4 +--
drivers/crypto/atmel-aes.c | 2 +-
drivers/crypto/axis/artpec6_crypto.c | 2 +-
drivers/crypto/cavium/cpt/cptvf_algs.c | 8 +++---
.../crypto/cavium/nitrox/nitrox_skcipher.c | 8 +++---
drivers/crypto/ccree/cc_cipher.c | 2 +-
.../crypto/marvell/octeontx/otx_cptvf_algs.c | 2 +-
.../marvell/octeontx2/otx2_cptvf_algs.c | 2 +-
include/crypto/xts.h | 25 +++++++------------
11 files changed, 23 insertions(+), 38 deletions(-)
base-commit: b6bb9676f2165d518b35ba3bea5f1fcfc0d969bf
--
2.38.1
next reply other threads:[~2022-12-29 20:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-29 20:37 Vladis Dronov [this message]
2022-12-29 20:37 ` [PATCH v2 1/6] crypto: xts - restrict key lengths to approved values in FIPS mode Vladis Dronov
2022-12-29 20:37 ` [PATCH v2 2/6] crypto: xts - drop xts_check_key() Vladis Dronov
2022-12-29 20:37 ` [PATCH v2 3/6] crypto: xts - drop redundant xts key check Vladis Dronov
2022-12-29 20:37 ` [PATCH v2 4/6] crypto: testmgr - disallow plain cbcmac(aes) in FIPS mode Vladis Dronov
2022-12-29 20:37 ` [PATCH v2 5/6] crypto: testmgr - disallow plain ghash " Vladis Dronov
2022-12-29 20:37 ` [PATCH v2 6/6] crypto: testmgr - allow ecdsa-nist-p256 and -p384 " Vladis Dronov
2022-12-29 21:01 ` Eric Biggers
2022-12-29 21:15 ` Vladis Dronov
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=20221229203708.13628-1-vdronov@redhat.com \
--to=vdronov@redhat.com \
--cc=davem@davemloft.net \
--cc=ebiggers@google.com \
--cc=elliott@hpe.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nstange@suse.de \
--cc=smueller@chronox.de \
/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