Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Josh Datko <jbdatko@gmail.com>
To: Dave Taht <dave.taht@gmail.com>,
	"cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] pcengines apu2c4 hardware random number generation
Date: Thu, 05 May 2016 10:10:37 -0600	[thread overview]
Message-ID: <1462464637.25803.30.camel@gmail.com> (raw)
In-Reply-To: <CAA93jw4PDKEApsZxKMed7Z6rq=DU=a4-zJEbJ=_8syF9Be_fzA@mail.gmail.com>

On Wed, 2016-05-04 at 16:28 -0700, Dave Taht wrote:
> so I figure that there might be something even simpler out there from
> the pi-ish or beaglebone world that could be repurposed to suit?

I've used Atmel's CryptoAuthentication chips routinely. They are i2c
based and have a (proprietary) RNG on them. I have a few linux driver
options for using them.

Presumably, you want this HWRNG thing to be inside the case. Looking at
that pdf, jumper J4 says it's an I2C connector. Those Atmel chips I was
playing with are all i2c, so you could try flywiring those to the
connector.

I'm not sure what pin is what, but PWR and GND should be easy to find
and then SDA/SCL I just plug and and try. If it doesn't work, swap the
pins.

As long as the CPU has access to that i2c bus, (is there an i2c-tools
equivalent on cerowrt?), then you should see it.

miniPCIe has I2C as well. I had this idea once to take a miniPCI card
and solder the atmel chips to the SDA/SCL lines.

8-pin molex connectors should be easy to find and it probably wouldn't
be too bad to make it a "proper" expansion board, but ... loose wires
make life more exciting :)

Josh

links:

Out-of-tree kernel driver for Atmel AT204/108/508 chips with /dev/hwrng
support: https://github.com/cryptotronix/atsha204-i2c

CLI application using the AT204: https://github.com/cryptotronix/hashle
t

Digikey: https://www.digikey.com/product-detail/en/atmel/ATECC508A-SSHD
A-B/ATECC508A-SSHDA-B-ND/5213053

^ The 204A are cheaper, the 508A have ECDSA/ECDH as well as the RNG and
my "eclet" driver will support ecdsa signing/ecdh, so might as well get
those vs. the 204A.




  parent reply	other threads:[~2016-05-05 16:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-04 23:28 Dave Taht
2016-05-05  0:16 ` Luis E. Garcia
2016-05-05  0:54   ` Dave Taht
2016-05-05 16:10 ` Josh Datko [this message]
2016-05-06 20:19   ` Dave Taht
2016-05-09 15:10     ` Josh Datko

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=1462464637.25803.30.camel@gmail.com \
    --to=jbdatko@gmail.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