Hi Christophe, As an ex-Oberthur, I might be a bit biased - yet I understand they're doing _very_ well with the US-DOD _because_ they're are no strings attached to their cards.
Still, I assume you'll always find a few glitches to unlock the card manager (key divesification algo) as mechanisms do have the tendancy to change from a company to another ... still, no need for any SDK to talk to a COSMO-64K for instance. Regards, Philippe On Monday 18 June 2007 03:53:10 Christophe Gudin wrote: > Hello Everyone, > > I'm having a little trouble to set up a smart card environment which is > totally opensource. My goal is to have a cryptographic sc which can store > one or preferably two or three certificates and perform basic rsa > operations. The card should be used for the key generation, authentication > and signing. Thus I believe a PKCS11 module would be great and easy to use > for this kind of usage. > > I've been testing a few cards lately, (Cyberflex, Cryptoflex and > GemSafeXpresso) to find after a few hours of testing that they require > proprietary SDK's in the case of the javacards. The Cryptoflex worked fine > with the opensc project, but I just heared Gemalto is planning on > discontinuing them this summer. > > Does anyone know about a card that is really "open" without the CodeShield > protection or anything else that forces the use of a proprietary SDK which > I could use with the Muscle Framework (or eventually with the opensc > project). > > Any help would be greatly appreciated, as I'm starting to feel that the > smart-card industry is pretty hostile to open source. > > Best Regards, > > Christophe Gudin. > > PS: I'm cross-posting this message on the opensc mailing list, as their > non-java cards project also has a PKCS11 module... -- _________________________ Philippe C. Martin +1 405 562 7005 www.snakecard.com _________________________ _______________________________________________ Muscle mailing list [email protected] http://lists.drizzle.com/mailman/listinfo/muscle
