From: Stephen Hemminger <stephen@networkplumber.org>
To: Dave Taht <dave.taht@gmail.com>
Cc: Stephan Mueller <smueller@chronox.de>,
Stephen Walker <stephendwalker@gmail.com>,
"cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>,
Felix Fietkau <nbd@nbd.name>
Subject: Re: [Cerowrt-devel] New random number generator for linux...
Date: Thu, 17 Oct 2013 17:57:05 -0700 [thread overview]
Message-ID: <20131017175705.3722c1f3@nehalam.linuxnetplumber.net> (raw)
In-Reply-To: <CAA93jw6En79onANmLrTqoDnko56vySKQYnGk=f2agrvHXYCOwg@mail.gmail.com>
On Thu, 17 Oct 2013 17:40:37 -0700
Dave Taht <dave.taht@gmail.com> wrote:
> This new design for a rng actually appears to be pretty reasonable.
>
> http://thread.gmane.org/gmane.linux.kernel.cryptoapi/9878
>
> Full details, paper, and code patches here:
>
> http://www.chronox.de/
>
> I am (as usual) low on time to package it up for openwrt, or patch it
> into the kernel, and try it. I will probably be able to get around to
> it next weekend if nobody beats me to it, slamming it into my pie
> build for x86 first.
>
> I'd be very interested if some folk could compare the standalone
> daemon to rngd on their favorite platform? And if anyone here has the
> chops to think hard about the algo, that would be nice, too...
>
> In other news , theodore ts'o's got a whole bunch more new patches for
> the random driver on kernel.org that I HAVE patched in and am trying
> to get into the next cero release. Fixes for get_cycles(), arrived
> already in mainline, and the mips patch is around somewhere.
>
> While that stuff improves the quality of the entropy in the system,
> the above rng would bring *more* entropy into the system, maybe get
> rid of the existing daemon (or integrate with it) and/or hostapd
> patches, etc, which I find exciting. That said, validating rng stuff
> is *hard*.
>
I would not trust it until accepted upstream.
It is better to mix multiple sources in rather than just relying on
any single source. That way it makes it harder for organizations to
poison the well.
next prev parent reply other threads:[~2013-10-18 0:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-18 0:40 Dave Taht
2013-10-18 0:57 ` Stephen Hemminger [this message]
2013-10-18 1:20 ` Dave Taht
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
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20131017175705.3722c1f3@nehalam.linuxnetplumber.net \
--to=stephen@networkplumber.org \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=nbd@nbd.name \
--cc=smueller@chronox.de \
--cc=stephendwalker@gmail.com \
/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