From: Herbert Xu <herbert@gondor.apana.org.au>
To: "Stephan Müller" <smueller@chronox.de>
Cc: linux-crypto@vger.kernel.org
Subject: Re: [PATCH] crypto: Jitter RNG - Permanent and Intermittent health errors
Date: Fri, 24 Mar 2023 17:27:37 +0800 [thread overview]
Message-ID: <ZB1tCY3ruqvtWfHS@gondor.apana.org.au> (raw)
In-Reply-To: <12194787.O9o76ZdvQC@positron.chronox.de>
On Thu, Mar 23, 2023 at 08:17:14AM +0100, Stephan Müller wrote:
>
> @@ -138,29 +139,35 @@ static int jent_kcapi_random(struct crypto_rng *tfm,
>
> spin_lock(&rng->jent_lock);
>
> - /* Return a permanent error in case we had too many resets in a row. */
> - if (rng->reset_cnt > (1<<10)) {
> + /* Enforce a disabled entropy source. */
> + if (rng->disabled) {
> ret = -EFAULT;
> goto out;
> }
Can we please get rid of this completely when we're not in FIPS
mode? Remember that jent is now used by all kernel users through
drbg. Having it fail permanently in this fashion is unacceptable.
If we're not in FIPS mode it should simply carry on or at least
seek another source of entropy, perhaps from the kernel RNG.
Thanks,
--
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
next prev parent reply other threads:[~2023-03-24 9:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-23 7:17 [PATCH] crypto: Jitter RNG - Permanent and Intermittent health errors Stephan Müller
2023-03-24 9:27 ` Herbert Xu [this message]
2023-03-24 12:01 ` Stephan Mueller
2023-03-24 12:30 ` [PATCH v2] " Stephan Müller
2023-03-24 16:03 ` kernel test robot
2023-03-24 17:00 ` [PATCH v3] " Stephan Müller
2023-03-24 17:47 ` Vladis Dronov
2023-03-24 17:54 ` Stephan Mueller
2023-03-25 14:44 ` Vladis Dronov
2023-03-26 8:51 ` Stephan Müller
2023-03-27 7:03 ` [PATCH v4] crypto: jitter - permanent and intermittent " Stephan Müller
2023-03-27 16:40 ` Marcelo Henrique Cerri
2023-04-06 8:50 ` 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=ZB1tCY3ruqvtWfHS@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.