public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andy Lutomirski <luto@amacapital.net>
To: "Theodore Ts'o" <tytso@mit.edu>, Greg Price <price@mit.edu>
Cc: Matt Mackall <mpm@selenic.com>,
	Herbert Xu <herbert@gondor.apana.org.au>,
	tpmdd-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org,
	Andy Lutomirski <luto@amacapital.net>
Subject: [PATCH resend 0/2] random: Use DRBG sources
Date: Mon, 14 Apr 2014 08:49:58 -0700	[thread overview]
Message-ID: <cover.1397487345.git.luto@amacapital.net> (raw)

[Resent because I forgot to email lkml.  This also surreptitiously
 fixes a silly typo on a patch description.]

This is my attempt to come up with a workable way to use so-called
entropy sources like a TPM to feed /dev/urandom.

Arguably we should be feeding the input pool as well, but if the
/dev/random algorithm is correct, this shouldn't matter.  I don't want
sensible use of TPMs for /dev/urandom to block on a long debate about
/dev/random, so these patches have no effect on /dev/random.

Andy Lutomirski (2):
  random: Add add_drbg_randomness to safely seed urandom from crypto hw
  tpm,random: Call add_drbg_randomness after selftest

 drivers/char/random.c            | 56 +++++++++++++++++++++++++++++++++++-----
 drivers/char/tpm/tpm-interface.c | 15 ++++++++++-
 include/linux/random.h           |  1 +
 include/trace/events/random.h    | 19 ++++++++++++++
 4 files changed, 83 insertions(+), 8 deletions(-)

-- 
1.9.0


             reply	other threads:[~2014-04-14 15:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-14 15:49 Andy Lutomirski [this message]
2014-04-14 15:49 ` [PATCH resend 1/2] random: Add add_drbg_randomness to safely seed urandom from crypto hw Andy Lutomirski
2014-04-14 15:50 ` [PATCH resend 2/2] tpm,random: Call add_drbg_randomness after selftest Andy Lutomirski
2014-04-14 16:13 ` [PATCH resend 0/2] random: Use DRBG sources Torsten Duwe
2014-04-14 16:36   ` Andy Lutomirski
2014-04-14 17:22 ` Andy Lutomirski

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=cover.1397487345.git.luto@amacapital.net \
    --to=luto@amacapital.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mpm@selenic.com \
    --cc=price@mit.edu \
    --cc=tpmdd-devel@lists.sourceforge.net \
    --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