----- Original Message ----- From: "Peter Stamfest" <[EMAIL PROTECTED]>
To: "MUSCLE" <[EMAIL PROTECTED]>
Sent: Monday, November 29, 2004 11:22 AM
Subject: [Muscle] Questions regarding the Muscle cardedge protocol
Hi,
as you may have noticed I'm snooping around quite a bit...
good! I dont think much has changed from 2001...
All we really have to do is add an IDL descriptor for every stream and method , and indicate non-support for 28 bio formats that the the card doesnt support, and it will be updated to match the GSC-IS grade of functionality! Then we charge the US govt $50 a card, via a defense contractor, on the grounds that the lab version was evaluated as compliant with the procurement offices protection profile (version 2001).
To be serious, what I find wonderful about the applet is its sheer economy - in doing 80% of what anyone wants from a cryptocard: all on a $4 USB chip, with 3 very simple packages that have required no maintenance in 3 years!
By only supporting partial API mapping of PKCS#11 (versus the full object model), the 80% function address the major personal security application that anyone actually uses today, on PCs.
Does anyone know of a shipping javacard chip that natively supports I2C signalling, BTW? I want to dump the 7816 signalling overhead. With uP chips made in the last 2 years, from the latest fabs, we really dont need all that reliability overhead, when the chip is part of a USB-enabled controller+javacard dongle.
Peter. _______________________________________________
Muscle mailing list
[EMAIL PROTECTED]
http://lists.drizzle.com/mailman/listinfo/muscle
