[Hardware] "success"

[Jim C. Nasby]

On Wed, Oct 18, 2006 at 01:51:43PM -0600, John L. Bass wrote:
> 	Out of curiosity... is there any way to safely embed our encrypt/decrypt
> 	functions in that code without it becomming public? Otherwise I'm not
> 	sure how we'd be able to plug one of these in to the network...
> 
> The answer is still effectively no. There would have to be a standard
> hardware configuration to freeze it. Or at least a fixed set of cores
> for every usable FPGA, which at least in the beginning would require
> releasing the crypto to a half dozen or better FPGA developers (most
> of the FPGA RC5 user community).

Well, anyone who's willing to sign an NDA can become 'staff' and get
full CVS access, so maybe that's not beyond reason.

> 	On Wed, Oct 18, 2006 at 12:55:32PM -0600, Olivier Meyer wrote:
> 	> >I just thought I'd let you guys know since this seems to be a 4 msgs a
> 	> >year mailing list :-)
> 
> Which is why this list is dead. The proprietary interests block open
> access.

Ideas for ways to do away with the crypto most welcome. :)
-- 
Jim C. Nasby, Database Architect            decibel at distributed.net
Give your computer some brain candy! www.distributed.net Team #1828

Windows: "Where do you want to go today?"
Linux: "Where do you want to go tomorrow?"
FreeBSD: "Are you guys coming, or what?"