[Cryptography] Use of RDRAND in Haskell's TLS RNG?
marksteward at gmail.com
Sat Nov 26 08:04:18 EST 2016
Links below taken from
Here's a diagram which shows what we're offered:
Arnold is saying that if we had access to the output of "Hardware Entropy
Source" it might be possible to verify the quality of that data, and to get
confidence that the intervening steps aren't subverted by default. As it
is, we have a black box, and there's nothing that prevents some secret
trigger wiring the DRBG input to a counter.
The black box does its own testing which is exposed by the carry flag:
The "Online Entropy Health Tests" have a 256*256bit buffer of entropy,
which is used to sanity check the input and return an error, but which
isn't exposed outside of test processors. This also means the DRNG will by
design fail and return 0 for an uncontrollable subset of inputs.
There's some more detail in
(search for "mostly stuck at 1" for an interesting point).
On Sat, Nov 26, 2016 at 5:41 AM, Viktor Dukhovni <cryptography at dukhovni.org>
> > On Nov 25, 2016, at 3:55 PM, Arnold Reinhold <agr at me.com> wrote:
> > In addition the need for a proper published audit that bear suggested,
> the most glaring defect in the Intel design is the lack of access to the
> un-whitened random bits. Adding a mode that bypassed the whitener would
> have been simple. Statistical analysis of the raw bit stream can provide
> ongoing assurance that the RNG is doing what it says. Likely there will be
> correlations between raw bit statistics and external parameters such as
> chip temperature and supply voltage. Of course it is possible for a
> deterministic generator to mimic such variations, but it would have to have
> a relatively large footprint on the die compared to simply using the
> whitener in a feedback mode or similar mischief.
> It seems you're hinting at:
> RDSEED first appears in Broadwell CPUs, while RDRAND appears earlier in
> Ivy Bridge.
> The cryptography mailing list
> cryptography at metzdowd.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the cryptography