[onerng talk] install & access

[Paul Campbell]

On Tue, 28 Oct 2014 10:29:45 ianG wrote:
> Now that we're getting close to production runs, and as I haven't paid
> attention, what is the situation for us lot in user-land?

linux is working - there's a UDEV script that's triggered by that verifies the 
device's integrity (I'll release that code this week though you all have 
unsigned images in your devices so you'll have to disable the check) it starts 
rngd a standard linux daemon for feeding the kernel entropy pool

Windows has been somewhat intractable (the APIs for feeding entropy are not 
documented if they exist)

Someone is looking at the MacOS side 
 
> My ideal scenario is that you plug it in and it exposes a device of some
> form, either a 'disk file' or a tty.  That's because those are easy to
> deal with in a script or program.

it's a tty - set it to raw and it listens for commands and responds with a 
byte stream

> Related question is whether a driver or program needs to be installed.
> That is a significant cost to use, and I'd encourage exploring ways to
> get around that, but not sure what they are as yet.

it uses the standard ACM class tty driver - Linux, Windows and macOS all come 
with the kernel driver as standard/built in - it's been tested and works on 
all 3 platforms

They'll all need some user app - in the linux world you install a .rpm or .deb 
- the released files contain no actual compiled code so they're nice and 
portable

	Paul