Re: [PATCH v2] DRBG: remove check for uninitialized DRBG handle

From: Stephan Mueller
Date: Tue Sep 02 2014 - 21:33:30 EST


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@xxxxxxxxxx>
> ---
> 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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/