public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	lkml <linux-kernel@vger.kernel.org>,
	linux-omap@vger.kernel.org, Kay Sievers <kay.sievers@vrfy.org>
Subject: Re: [patch 2.6.25-rc8] omap_rng minor updates
Date: Wed, 16 Apr 2008 10:04:49 -0700	[thread overview]
Message-ID: <200804161004.50075.david-b@pacbell.net> (raw)
In-Reply-To: <20080416112517.GA29220@gondor.apana.org.au>

On Wednesday 16 April 2008, Herbert Xu wrote:
> > Minor cleanups to the OMAP RNG:
> 
> Thanks.  I've picked this up in cryptodev-2.6.

Is that where the RNG stuff is now getting maintained?


If so, I wonder what should be done with some other
RNG changes sitting in one of my trees.  Briefly,
their initializations come late ... and after kernel
code has already started to use the kernel pool.  So
attacks based on known RNG patterns are possible at
that time.

So the patch I had -- needs reworking -- moves the
RNG driver initializations earlier, and uses the
first one to seed the kernel pool.  Cryptographically
that would be no worse than the current situation (even
if you don't wholly trust the RNG), and in most cases
would be a distinct improvement.

- Dave

  reply	other threads:[~2008-04-16 17:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-11  4:32 [patch 2.6.25-rc8] omap_rng minor updates David Brownell
2008-04-16 11:25 ` Herbert Xu
2008-04-16 17:04   ` David Brownell [this message]
2008-04-17  3:30     ` 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=200804161004.50075.david-b@pacbell.net \
    --to=david-b@pacbell.net \
    --cc=akpm@linux-foundation.org \
    --cc=herbert@gondor.apana.org.au \
    --cc=kay.sievers@vrfy.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox