Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: dpreed@reed.com
To: "Dave Taht" <dave.taht@gmail.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] hwrngs
Date: Sun, 2 Feb 2014 11:17:21 -0500 (EST)	[thread overview]
Message-ID: <1391357841.349720412@apps.rackspace.com> (raw)
In-Reply-To: <CAA93jw4Q=P=Yd_Uqt6XiSsCAH+t_cWyBw6b6uyFFLS1a9Qgrvg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1362 bytes --]


Any idea what the price will be in quantity?   The fact that it supports both BB black and RPi is great news for makers interested in authentication and security.
 


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
>

[-- Attachment #2: Type: text/html, Size: 1857 bytes --]

  reply	other threads:[~2014-02-02 16:17 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 [this message]
2014-02-02 16:25   ` Dave Taht
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=1391357841.349720412@apps.rackspace.com \
    --to=dpreed@reed.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dave.taht@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