From: Stephan Mueller <smueller@chronox.de>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Linux Crypto Mailing List <linux-crypto@vger.kernel.org>
Subject: Re: DRBG seeding
Date: Thu, 16 Apr 2015 17:07:20 +0200 [thread overview]
Message-ID: <1505308.pr7rreheuo@tauon> (raw)
In-Reply-To: <20150416143617.GA17178@gondor.apana.org.au>
Am Donnerstag, 16. April 2015, 22:36:17 schrieb Herbert Xu:
Hi Herbert,
>Hi Stephan:
>
>Currently DRBG is seeded with entropy from get_random_bytes.
>However, get_random_bytes is basically the kernel version of
>/dev/urandom. So there is no guarantee that you're actually
>getting the amount of entropy required.
>
>Are you sure this is compliant with the DRBG specification?
I do not see a specific requirement in SP800-90A about the quality of the
noise source.
But SP800-90B specifies tests and assessments about the quality. When applying
that specification, I applied some initial assessments: /dev/urandom complies
with SP800-90B when disregarding the very early boot stage (i.e. when assuming
that the input_pool received sufficient entropy).
The only shaky time is the boot time until the nonblocking_pool/input_pool has
been sufficiently seeded.
That said, I already developed an in-kernel version of /dev/random. I sent the
patch to LKML some half year ago. If I understood Ted Tso right, there is no
general objection against adding that in-kernel interface. See [1] for the
thread.
Furthermore, I already started working on updating the DRBG to use that in-
kernel /dev/random interface.
Shall I pursue that work in earnest now?
[1] https://lkml.org/lkml/2014/5/11/276
Ciao
Stephan
next prev parent reply other threads:[~2015-04-16 15:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-16 14:36 DRBG seeding Herbert Xu
2015-04-16 15:07 ` Stephan Mueller [this message]
2015-04-16 15:26 ` Herbert Xu
2015-04-16 15:32 ` Stephan Mueller
2015-04-16 17:11 ` Andreas Steffen
2015-04-17 1:19 ` Stephan Mueller
2015-04-17 2:14 ` Herbert Xu
2015-04-17 12:48 ` Stephan Mueller
2015-04-17 13:11 ` Herbert Xu
2015-04-17 13:22 ` Stephan Mueller
2015-04-18 1:27 ` Herbert Xu
2015-04-18 1:32 ` Stephan Mueller
2015-04-18 1:36 ` Herbert Xu
2015-04-18 2:04 ` Stephan Mueller
2015-04-18 2:16 ` 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=1505308.pr7rreheuo@tauon \
--to=smueller@chronox.de \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
/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.