From: Herbert Xu <herbert@gondor.apana.org.au>
To: Stephan Mueller <smueller@chronox.de>
Cc: Ted Tso <tytso@mit.edu>,
andreas.steffen@strongswan.org, sandyinchina@gmail.com,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] crypto: drbg - Use callback API for random readiness
Date: Tue, 9 Jun 2015 21:24:38 +0800 [thread overview]
Message-ID: <20150609132438.GA12946@gondor.apana.org.au> (raw)
In-Reply-To: <3448831.Xm980FM7Uq@tachyon.chronox.de>
On Tue, Jun 09, 2015 at 02:23:39PM +0200, Stephan Mueller wrote:
>
> I am wondering about the error here. The Jitter RNG has in its init function a
> test to see whether the RNG really works on the hardware as there are still
> systems out there that have no high-res timer (e.g. I have seen that on old
> Android phones). If the Jitter RNG detects that the system is not appropriate,
> it will not register.
If we have no jent and the pool isn't ready then we should at least
fail in FIPS mode. If we weren't in FIPS mode we could block but
for now I'm going to go with the current behaviour of simply
continuing.
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:[~2015-06-09 13:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-06 2:16 [PATCH] crypto: use list to stage async seeding requests Stephan Mueller
2015-06-09 6:49 ` Herbert Xu
2015-06-09 10:18 ` [PATCH 0/3] random: Replace kernel blocking API with callback API Herbert Xu
2015-06-09 10:19 ` [PATCH 1/3] random: Add callback API for random pool readiness Herbert Xu
2015-06-09 10:19 ` [PATCH 2/3] crypto: drbg - Use callback API for random readiness Herbert Xu
2015-06-09 12:23 ` Stephan Mueller
2015-06-09 13:24 ` Herbert Xu [this message]
2015-06-09 10:19 ` [PATCH 3/3] random: Remove kernel blocking API Herbert Xu
2015-06-09 10:21 ` [PATCH 2/3] crypto: drbg - Use callback API for random readiness Herbert Xu
2015-06-09 13:55 ` 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=20150609132438.GA12946@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=andreas.steffen@strongswan.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sandyinchina@gmail.com \
--cc=smueller@chronox.de \
--cc=tytso@mit.edu \
/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®