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:32:27 +0200 [thread overview]
Message-ID: <2037814.HNld8WWmfI@tauon> (raw)
In-Reply-To: <20150416152618.GA17690@gondor.apana.org.au>
Am Donnerstag, 16. April 2015, 23:26:18 schrieb Herbert Xu:
Hi Herbert,
>On Thu, Apr 16, 2015 at 05:07:20PM +0200, Stephan Mueller wrote:
>> I do not see a specific requirement in SP800-90A about the quality of the
>> noise source.
>
>Well it explicitly says that you cannot use a DRBG. In the worst
>case get_random_bytes is completely deterministic.
>
>> 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
>
>Yes I think we should do this.
Ok, I will work on that after I added the global lock to the DRBG.
>
>Thanks,
Ciao
Stephan
next prev parent reply other threads:[~2015-04-16 15:32 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
2015-04-16 15:26 ` Herbert Xu
2015-04-16 15:32 ` Stephan Mueller [this message]
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=2037814.HNld8WWmfI@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.