From: Theodore Ts'o <tytso@mit.edu>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Linux Kernel Developers List <linux-kernel@vger.kernel.org>,
linux-crypto@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH] random: limit the contribution of the hw rng to at most half
Date: Fri, 18 Jul 2014 02:23:56 -0400 [thread overview]
Message-ID: <20140718062356.GC1491@thunk.org> (raw)
In-Reply-To: <53C85D50.5040901@zytor.com>
On Thu, Jul 17, 2014 at 04:33:36PM -0700, H. Peter Anvin wrote:
>
> I just want to make sure we don't negatively impact the real security of
> users because of "optics". We already have a lot of problems with
> people extracting long-living keys from /dev/urandom because /dev/random
> is too slow.
With a system with RDRAND, we're mixing arch_get_rand_long() as part
of the extraction process (as the seed for the SHA's IV). So if you
trust RDRAND, then using /dev/urandom even when the entropy count is
zero is going to be secure. If you don't trust RDRAND, then the
RDSEED entropy accounting is going to be extremely disturbing.
So the only way that we could be impacting the "real security" of
users, would be if RDRAND was back-doored, but RDSEED wasn't. And
that doesn't seem like a terribly likely scenario to me, but what do I
know? :-)
- Ted
prev parent reply other threads:[~2014-07-18 7:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-17 10:03 [PATCH] random: limit the contribution of the hw rng to at most half Theodore Ts'o
2014-07-17 17:39 ` H. Peter Anvin
2014-07-17 22:08 ` Theodore Ts'o
2014-07-17 23:33 ` H. Peter Anvin
2014-07-18 6:23 ` Theodore Ts'o [this message]
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=20140718062356.GC1491@thunk.org \
--to=tytso@mit.edu \
--cc=hpa@zytor.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).