From: Stephan Mueller <smueller@chronox.de>
To: Theodore Ts'o <tytso@mit.edu>
Cc: Sandy Harris <sandyinchina@gmail.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
linux-crypto@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] random: add random_initialized command line param
Date: Wed, 20 May 2015 18:18:01 +0200 [thread overview]
Message-ID: <9811880.Zfx1jXMqj8@tauon> (raw)
In-Reply-To: <20150520150642.GJ2871@thunk.org>
Am Mittwoch, 20. Mai 2015, 11:06:42 schrieb Theodore Ts'o:
Hi Theodore,
As a side note to this discussion, may I ask why entropy_total is used for
checking against the threshold value and not entropy_count?
The reason for my question is the following: until a DRNG (in the worst case,
nonblocking_pool is a DRNG) is fully seeded, partial seeds may be "eaten" up
by the caller.
For the discussion, let us assume the worst case that there is coming in one
bit of entropy at a time. In between the addition of each bit of entropy, an
attacker can access the DRNG (i.e. the SHA1 output of the nonblocking_pool).
When only one bit of entropy is added to the nonblocking_pool, the attack
complexity would be 1 bit. When an attacker would access the nonblocking_pool
after each received bit, in the worst case, the attack complexity is not
2**128 but rather 256 (i.e. 1 bit for each individual attack between the
addition of one new bit of entropy).
So, the total attack complexity is the sum of the individual attack
complexities (i.e. the complexity added after the previous attack is
performed).
When using the entropy_count variable which is affected by account() (i.e. it
is decreased when a reader obtains data), the threshold is only reached when
truly 128 unobserved bits are collected.
Ciao
Stephan
next prev parent reply other threads:[~2015-05-20 16:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-18 16:25 [PATCH] random: add random_initialized command line param Stephan Mueller
2015-05-18 18:42 ` Theodore Ts'o
2015-05-18 19:16 ` Stephan Mueller
2015-05-18 22:58 ` Herbert Xu
2015-05-19 22:40 ` Sandy Harris
2015-05-20 6:29 ` Stephan Mueller
2015-05-20 15:06 ` Theodore Ts'o
2015-05-20 16:18 ` Stephan Mueller [this message]
2015-06-23 20:44 ` Pavel Machek
2015-06-23 21:47 ` Stephan Mueller
2015-06-24 8:45 ` Pavel Machek
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=9811880.Zfx1jXMqj8@tauon \
--to=smueller@chronox.de \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sandyinchina@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).