From: Dave Taht <dave.taht@gmail.com>
To: Rick Jones <rick.jones2@hp.com>
Cc: esr@thyrsus.com, Eric Raymond <esr@snark.thyrsus.com>,
bloat-devel@lists.bufferbloat.net
Subject: Re: Preliminary results of using GPS to look for clock skew
Date: Thu, 22 Sep 2011 10:34:03 -0700 [thread overview]
Message-ID: <CAA93jw7=yeE_WdkF8Gum32D4SX06HSXfB5qiq4_6fBpOxckzNg@mail.gmail.com> (raw)
In-Reply-To: <4E7B6D48.2040205@hp.com>
On Thu, Sep 22, 2011 at 10:15 AM, Rick Jones <rick.jones2@hp.com> wrote:
>
>>
>> One thing that surprised me of late is
>> http://www.bufferbloat.net/issues/271
>>
>> while not related, surprises are the last thing we need as regards to
>> time.
>>
>
> The decision to stop letting networking contribute to entropy goes back a
> few years actually :)
I wasn't paying attention then.
> In another context, also where running-out of entropy was a problem, someone
> mentioned there are RNGs on USB keys that can be used to provide
> randomness/entropy/whatnot. The one mentioned in that discussion was the
> "Entropy Key" from these folks: http://www.entropykey.co.uk/
While I would like RNGs to be on-chip, the lack of randomness in a system
that supposedly does a lot of WPA encryption does concern me.
https://dev.openwrt.org/ticket/9631
Secondly, routers at least have multiple interfaces to get randomness from
which would be hard to spoof all at the same time.
and wireless routers have more noise sources and interfaces...
so while I find the decision to eliminate networking as a source of randomness
makes some sense in a device with only one interface, I find it indefensible to
have nearly no entropy pool at all as a result for devices with
multiple interfaces.
> rick jones
>
--
Dave Täht
SKYPE: davetaht
US Tel: 1-239-829-5608
http://the-edge.blogspot.com
next prev parent reply other threads:[~2011-09-22 17:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-21 23:02 Eric Raymond
2011-09-22 0:18 ` Dave Taht
2011-09-22 2:11 ` Eric Raymond
2011-09-22 2:24 ` Jonathan Morton
2011-09-22 2:29 ` Eric Raymond
2011-09-23 9:09 ` Jan Ceuleers
2011-09-23 9:38 ` Dave Taht
2011-09-23 12:10 ` Jan Ceuleers
2011-09-23 12:50 ` Rick
2011-09-24 14:50 ` Jan Ceuleers
2011-09-22 9:08 ` Dave Taht
2011-09-22 17:15 ` Rick Jones
2011-09-22 17:34 ` Dave Taht [this message]
2011-09-22 17:43 ` Rick Jones
2011-09-22 17:58 ` Dave Taht
2011-09-23 10:57 ` Aidan Williams
2011-09-23 10:10 ` Dave Taht
2011-09-23 9:09 ` Jan Ceuleers
2011-09-23 9:24 ` Jan Ceuleers
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='CAA93jw7=yeE_WdkF8Gum32D4SX06HSXfB5qiq4_6fBpOxckzNg@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=bloat-devel@lists.bufferbloat.net \
--cc=esr@snark.thyrsus.com \
--cc=esr@thyrsus.com \
--cc=rick.jones2@hp.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