All of lore.kernel.org
 help / color / mirror / Atom feed
From: Herbert Xu <herbert@gondor.apana.org.au>
To: Stephan Mueller <smueller@chronox.de>
Cc: Andreas Steffen <andreas.steffen@strongswan.org>,
	Linux Crypto Mailing List <linux-crypto@vger.kernel.org>
Subject: Re: DRBG seeding
Date: Fri, 17 Apr 2015 21:11:37 +0800	[thread overview]
Message-ID: <20150417131137.GA27060@gondor.apana.org.au> (raw)
In-Reply-To: <2956307.5uMbChcz7z@myon.chronox.de>

On Fri, Apr 17, 2015 at 02:48:51PM +0200, Stephan Mueller wrote:
>
> Do you really think that this is possible? If the DRBG becomes the stdrng, you 
> would imply that those callers (e.g. IPSEC) may suffer from a long block (and 
> with long I mean not just seconds, but minutes).

It's only 49 bytes for every 64K so I think it's reasonable.
The only reason someone would use this is to comply with the
standard and this is what the standard requires so I don't see
how we can do anything else.
 
> Furthermore, I fail to see the difference between the current default stdrng 
> (krng -- which is just get_random_bytes in disguise). Thus, the current 
> situation with the DRBG seeding is not different from the non-DRBG use case.

The difference is that krng doesn't have to satisfy any standard.

Cheers,
-- 
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

  reply	other threads:[~2015-04-17 13:11 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
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 [this message]
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=20150417131137.GA27060@gondor.apana.org.au \
    --to=herbert@gondor.apana.org.au \
    --cc=andreas.steffen@strongswan.org \
    --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.