Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: David Reed <dpreed@reed.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>,
	Joshua Datko <jbdatko@gmail.com>
Subject: Re: [Cerowrt-devel] hwrngs
Date: Sun, 2 Feb 2014 08:25:01 -0800	[thread overview]
Message-ID: <CAA93jw6h+ev_7U7_SjDohpoaSEREfHkvcE3N8qwrkyDCzbZMqg@mail.gmail.com> (raw)
In-Reply-To: <1391357841.349720412@apps.rackspace.com>

On Sun, Feb 2, 2014 at 8:17 AM,  <dpreed@reed.com> wrote:
> Any idea what the price will be in quantity?

No. Pretty cheap, it's a very tiny board....

http://cryptotronix.com/2013/12/27/hashlet_random_tests/

I got a discount for 5, and he has a couple left...

> The fact that it supports
> both BB black and RPi is great news for makers interested in authentication
> and security.

yep.

It is open hardware also, with a schematic supplied, open source
driver (not a kernel driver yet), I was very happy to support this
project.

I have looked for usb equivalents, btw, and haven't found anything
inexpensive. And in the case of cero I'd wanted something that could
run
on the internal serial header...

I note that theoretically the BBB also has an on-cpu hwrng but
documentation on it from TI is lacking. Perhaps someone could lean on
TI to free that information up in the post-snowden era?

(my take on it is the more hwrngs the better, one from china, one from
russia, one from the USA...)

/me goes back to converting his dns/mail/vpn server over to a BBB....

>
>
>
>
>
> On Saturday, February 1, 2014 11:11pm, "Dave Taht" <dave.taht@gmail.com>
> said:
>
>> I am still quite irked by having to use /dev/urandom for important
>> tasks like dnssec key generation, and in wireless WPA. And like
>> others, distrust having only one source of random numbers in the mix.
>>
>> I just ordered some of these
>>
>> http://cryptotronix.com/2013/12/27/hashlet_random_tests/
>>
>> Simultaneously while I was getting nsupdate dns working on cerowrt
>> from the yurt to the dynamic ipv6 stuff, my main dns server died, and
>> I decided
>> I'd move dns to a beaglebone black, so running across this hwrng made
>> me feel better about randomness on embedded systems.
>>
>> I bought the last 5 Joshua had, sorry about that! I'd like to find
>> something
>> that could run off the internal serial port on the wndr3800s... and
>> worth incorporating in future designs. (multiple vendors)
>>
>> --
>> Dave Täht
>>
>> Fixing bufferbloat with cerowrt:
>> http://www.teklibre.com/cerowrt/subscribe.html
>> _______________________________________________
>> Cerowrt-devel mailing list
>> Cerowrt-devel@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>>



-- 
Dave Täht

Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html

  reply	other threads:[~2014-02-02 16:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-02  4:11 Dave Taht
2014-02-02 16:17 ` dpreed
2014-02-02 16:25   ` Dave Taht [this message]
2014-02-02 16:45     ` dpreed

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=CAA93jw6h+ev_7U7_SjDohpoaSEREfHkvcE3N8qwrkyDCzbZMqg@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dpreed@reed.com \
    --cc=jbdatko@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