From: Stephan Mueller <smueller@chronox.de>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] DRBG: remove check for uninitialized DRBG handle
Date: Wed, 03 Sep 2014 03:33:16 +0200 [thread overview]
Message-ID: <3575659.BooajjTQie@myon.chronox.de> (raw)
In-Reply-To: <1461606.SUPpCYm782@myon.chronox.de>
Am Montag, 1. September 2014, 07:11:20 schrieb Stephan Mueller:
Hi Herbert,
may I ask for consideration of this patch as this covers an oops FIPS mode?
In addition, may I ask for guidance on how to fix the 32 bit code path in
Linus' tree as asked on 28.8? To quote: "Thus, the fix in
b9347aff91ce4789619168539f08202d8d6a1177 works. However, this
patch is based on 05c81ccd9087d238c10b234eadb55632742e5518. So, if we want to
fix Linus' tree with minimal impact, either these two patches are pushed to
Linus or I have to port b9347aff91ce4789619168539f08202d8d6a1177 to the
current Linus tree."
Thanks a lot
Stephan
> The drbg_healthcheck() contained a test to call the DRBG with an
> uninitialized DRBG cipher handle. As this is an inappropriate use of the
> kernel crypto API to try to generate random numbers before
> initialization, checks verifying for an initialized DRBG have been
> removed in previous patches.
>
> Now, the drbg_healthcheck test must also be removed.
>
> Changes V2: Added patch marker to email subject line.
>
> Signed-off-by: Stephan Mueller <smueller@chronox.de>
> ---
> crypto/drbg.c | 3 ---
> 1 file changed, 3 deletions(-)
>
> diff --git a/crypto/drbg.c b/crypto/drbg.c
> index 39ed918..54cfd48 100644
> --- a/crypto/drbg.c
> +++ b/crypto/drbg.c
> @@ -1872,9 +1872,6 @@ static inline int __init drbg_healthcheck_sanity(void)
> /* overflow max addtllen with personalization string */
> ret = drbg_instantiate(drbg, &addtl, coreref, pr);
> BUG_ON(0 == ret);
> - /* test uninstantated DRBG */
> - len = drbg_generate(drbg, buf, (max_request_bytes + 1), NULL);
> - BUG_ON(0 < len);
> /* all tests passed */
> rc = 0;
--
Ciao
Stephan
next prev parent reply other threads:[~2014-09-03 1:33 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-26 6:14 linux-next: build warnings after merge of the crypto tree Stephen Rothwell
2014-08-26 6:38 ` Herbert Xu
2014-08-26 7:00 ` Stephan Mueller
2014-08-26 7:31 ` [PATCH] DRBG: fix bit shifting on 32 bit systems Stephan Mueller
2014-08-26 7:32 ` Herbert Xu
2014-08-26 7:37 ` Stephan Mueller
2014-08-26 8:06 ` [PATCH] DRBG: fix maximum value checks " Stephan Mueller
2014-08-26 8:08 ` Herbert Xu
2014-08-26 8:29 ` [PATCH v2] " Stephan Mueller
2014-08-26 8:43 ` Herbert Xu
2014-08-26 8:52 ` Stephan Mueller
2014-08-26 8:58 ` Herbert Xu
2014-08-26 9:36 ` Stephan Mueller
2014-08-27 13:35 ` Herbert Xu
2014-08-27 13:40 ` Stephan Mueller
2014-08-28 7:13 ` Stephan Mueller
2014-08-28 7:17 ` DRBG: remove test for uninitialized DRBG handle Stephan Mueller
2014-09-01 5:11 ` [PATCH v2] DRBG: remove check " Stephan Mueller
2014-09-03 1:33 ` Stephan Mueller [this message]
2014-09-03 23:21 ` Herbert Xu
2014-09-03 23:50 ` Stephan Mueller
2014-09-05 7:55 ` Herbert Xu
2014-09-05 11:25 ` Stephan Mueller
2014-09-05 8:13 ` 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=3575659.BooajjTQie@myon.chronox.de \
--to=smueller@chronox.de \
--cc=herbert@gondor.apana.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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