From: Stephan Mueller <smueller@chronox.de>
To: Sandy Harris <sandyinchina@gmail.com>
Cc: linux-crypto@vger.kernel.org, Theodore Ts'o <tytso@mit.edu>,
John Denker <jsd@av8n.com>
Subject: Re: Could this be applied to random(4)?
Date: Sun, 29 May 2016 21:20:11 +0200 [thread overview]
Message-ID: <3128607.kWjc3BaTVM@positron.chronox.de> (raw)
In-Reply-To: <CACXcFmm1q-Z3JSE79m5ak-a+tO50uQNUPwvq_ueei_b19qycJw@mail.gmail.com>
Am Freitag, 27. Mai 2016, 16:09:53 schrieb Sandy Harris:
Hi Sandy,
> On Fri, May 27, 2016 at 2:30 PM, Stephan Mueller <smueller@chronox.de>
wrote:
> > This document describes extractors. Those extractors are intended to
> > combine *independent* sources with weak entropy.
> >
> > None of our sources we have in add_*_randomness are independent.
>
> No, but it would be easy to get two independent sources, interrupts
> and some sort of timer jitter thing as in my maxwell, your jitter
> driver, havege, ...
I think I would concur with you here. From my LRNG code:
static int lrng_pdrbg_seed_internal(u8 *outbuf, u32 outbuflen, bool
fullentropy,
bool drain)
{
...
/*
* Concatenate the output of the noise sources. This would be the
* spot to add an entropy extractor logic if desired.
...
> --
> To unsubscribe from this list: send the line "unsubscribe linux-crypto" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
Ciao
Stephan
prev parent reply other threads:[~2016-05-29 19:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-27 17:38 Could this be applied to random(4)? Sandy Harris
2016-05-27 18:30 ` Stephan Mueller
2016-05-27 20:09 ` Sandy Harris
2016-05-29 19:20 ` Stephan Mueller [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=3128607.kWjc3BaTVM@positron.chronox.de \
--to=smueller@chronox.de \
--cc=jsd@av8n.com \
--cc=linux-crypto@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