From: Stephan Mueller <smueller@chronox.de>
To: Marcus Meissner <meissner@suse.de>
Cc: herbert@gondor.apana.org.au, davem@davemloft.net,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] crypto: allow rfc3686 aes-ctr variants in fips mode.
Date: Fri, 19 Feb 2016 15:29:30 +0100 [thread overview]
Message-ID: <181988892.jqsYzZjG1O@positron.chronox.de> (raw)
In-Reply-To: <1455885268-15054-1-git-send-email-meissner@suse.de>
Am Freitag, 19. Februar 2016, 13:34:28 schrieb Marcus Meissner:
Hi Marcus,
> RFC 3686 CTR in various authenc methods.
>
> rfc3686(ctr(aes)) is already marked fips compliant,
> so these should be fine.
>
> Signed-off-by: Marcus Meissner <meissner@suse.de>
Acked-by: Stephan Mueller <smueller@chronox.de>
> ---
> crypto/testmgr.c | 16 ++++++++++++++++
> 1 file changed, 16 insertions(+)
>
> diff --git a/crypto/testmgr.c b/crypto/testmgr.c
> index 190a290..5316d59 100644
> --- a/crypto/testmgr.c
> +++ b/crypto/testmgr.c
> @@ -2167,6 +2167,10 @@ static const struct alg_test_desc alg_test_descs[] =
> { }
> }
> }, {
> + .alg = "authenc(hmac(sha1),rfc3686(ctr(aes)))",
> + .test = alg_test_null,
> + .fips_allowed = 1,
> + }, {
> .alg = "authenc(hmac(sha224),cbc(des))",
> .test = alg_test_aead,
> .suite = {
> @@ -2239,6 +2243,10 @@ static const struct alg_test_desc alg_test_descs[] =
> { .test = alg_test_null,
> .fips_allowed = 1,
> }, {
> + .alg = "authenc(hmac(sha256),rfc3686(ctr(aes)))",
> + .test = alg_test_null,
> + .fips_allowed = 1,
> + }, {
> .alg = "authenc(hmac(sha384),cbc(des))",
> .test = alg_test_aead,
> .suite = {
> @@ -2270,6 +2278,10 @@ static const struct alg_test_desc alg_test_descs[] =
> { .test = alg_test_null,
> .fips_allowed = 1,
> }, {
> + .alg = "authenc(hmac(sha384),rfc3686(ctr(aes)))",
> + .test = alg_test_null,
> + .fips_allowed = 1,
> + }, {
> .alg = "authenc(hmac(sha512),cbc(aes))",
> .fips_allowed = 1,
> .test = alg_test_aead,
> @@ -2315,6 +2327,10 @@ static const struct alg_test_desc alg_test_descs[] =
> { .test = alg_test_null,
> .fips_allowed = 1,
> }, {
> + .alg = "authenc(hmac(sha512),rfc3686(ctr(aes)))",
> + .test = alg_test_null,
> + .fips_allowed = 1,
> + }, {
> .alg = "cbc(aes)",
> .test = alg_test_skcipher,
> .fips_allowed = 1,
Ciao
Stephan
next prev parent reply other threads:[~2016-02-19 14:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-19 12:34 Marcus Meissner
2016-02-19 14:29 ` Stephan Mueller [this message]
2016-02-27 19:33 ` 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=181988892.jqsYzZjG1O@positron.chronox.de \
--to=smueller@chronox.de \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=meissner@suse.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
all inboxes | Powered by JetHome®