> > If we go with TINI/TStik as a reference platform (which is the way I am
> > also leaning for a number of reasons) then we can use the iButton holder
> > clip that is present on most TINI/TStik socket boards to hold a JavaCard
> > compliant iButton that could handle our digital signing and verification
> > needs.
>
> That will significantly slow responces. The Java Buttons are far from fast
> and the data exchange over 1-wire is not too speedy as well. However, it
> is a valid option (and would allow me to use my Java buttons for something
> usefull :-)
>
> It does add significant cost to the product, Java iButtons are not cheap..
I think worth it though...
I was thinking about this last night, and though want can't use iButtons for
on-the-fly security, they could be used for unique key generation etc...
which would also have a high "cool-factor"... each production device would
have one, and it would also help uniquely identify the Outpost "nodes" when
multiple nodes where connected together.
You can't order java ibutton samples though, so I don't know where to pick
them up to play around a little...
- Brill
|
