From: "Theodore Ts'o" <tytso@mit.edu>
To: Christoph Anton Mitterer <calestyo@scientia.net>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: RNG: is it possible to spoil /dev/random by seeding it from (evil) TRNGs
Date: Thu, 4 Oct 2012 18:49:42 -0400 [thread overview]
Message-ID: <20121004224942.GA23970@thunk.org> (raw)
In-Reply-To: <1349357555.3396.15.camel@fermat.scientia.net>
On Thu, Oct 04, 2012 at 03:32:35PM +0200, Christoph Anton Mitterer wrote:
>
> When seeding the kernels entropy cache (which is then ultimately used
> for /dev/random), e.g. by (semi-)TRNGs like haveged[0],
> audio-entropyd[1], Simtec’s Entropy Key[2] or friends... can one spoil
> the randomness by that or is this impossible by design?
It is impossible by design. Or specifically, /dev/random was designed
so that it can be world-writeable, and an attacker can feed in any
kind of input he or she wants, and it will not allow the attacker to
know anything more about the state of the entropy pool than he or she
knew before they started mixing inputs in.
There are comments that go into more detail about the design in
drivers/char/random.c. Credit for the design goes to Colin Plumb, who
designed RNG in the original PGP 2.x implementation, BTW.
- Ted
next prev parent reply other threads:[~2012-10-04 22:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-04 13:32 RNG: is it possible to spoil /dev/random by seeding it from (evil) TRNGs Christoph Anton Mitterer
2012-10-04 22:49 ` Theodore Ts'o [this message]
2012-10-08 0:41 ` Christoph Anton Mitterer
2012-10-08 1:24 ` Theodore Ts'o
2012-10-10 1:09 ` Christoph Anton Mitterer
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=20121004224942.GA23970@thunk.org \
--to=tytso@mit.edu \
--cc=calestyo@scientia.net \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).