The ATR declares the device name (before any personalization changes alter the ATR), which declares the eeprom, and this implies the # and type of cryptomemory keysets that the device supports for xauth. The ATR format details are NDA, technically. A simple, no fuss NDA with Atmel solves that.
ventavia.com has custom javacard chips to implement the cryptomemory authentication scheme for sale/licensing, for embedded applications. E.g. a gambling terminal bears the quad-flat pack packaged javacard that allows the terminal's processor to authenticate cryptomemory-class smartcards.
The users token can be a classical ID-1 module (with cryptomemory die), or USB token in which the cryptomemory die is delivered in in chip-on-board form factor along with a USB controller behaving as a CCID class device (so the PC can also interact with , and do xauth, against the cryptomemory)
The "SAM" chip (a javacard) is about $7.5, in large volumes, and has a resource config designed to support a FIPS 201 world, with the PIV applets, tuned for embedded apps (not PC apps). ventavia has a 250$ board available for EE developers, designed for prototyping the javacard auth over 7816-1 or USB OTG links to the cryptomemory die.
From: "Strom Carlson" <[EMAIL PROTECTED]> Reply-To: MUSCLE <[email protected]> To: MUSCLE <[email protected]> Subject: [Muscle] Identifying Atmel CryptoMemory chip Date: Wed, 8 Mar 2006 10:15:10 -0800 I have a card here which I believe to be an Atmel CryptoMemory chip, although I have no clue as to which specific chip it is. Is there a fairly easy way to determine this? -- Strom Carlson http://www.stromcarlson.com/ _______________________________________________ Muscle mailing list [email protected] http://lists.drizzle.com/mailman/listinfo/muscle
_______________________________________________ Muscle mailing list [email protected] http://lists.drizzle.com/mailman/listinfo/muscle
