2012/6/12 helpcrypto helpcrypto <helpcry...@gmail.com> > Hello again Alejandro. > > The problem im currently having is conceptual, rather than technical. > > IIUC, the PKCS#15 standard defines a way of storing data into tokens. > Said so, i expect to ANY PKCS#15 compliant card work out of the box. > But seems it doesnt. > > Watching some card-* files in libopensc source i noticed sometimes > AID, ATR or even some apdus are needed. > Shouldnt PKCS#15 just work without having to build anything? > > I agree that a custom PK11 library involves much work than a PK15, but > i though it was a zero-cost solution. > > So, will i need to build a card-example.c file/others and start doing > a try-error process to make this card opensc supported? > > Thanks for your help. >
Sorry for being late, Maybe it's better that someone more implicated in OpenSC architecture would answer this question. Anyway, I will try it: PKCS15 define the way to store the keys and data objects in a smart card, but not define any way to authenticate users. PKCS11 define this way via *cryptoki* API. This API is used in 3rd party applications as Mozilla FF or Thunderbird. You can export keys from a smartcard via pkcs15-tool, but this not mean that you don't need card-**.c driver to use it. This file will be so long than the card's API diff with ISO 7816 standard[1]. To known this diff you need card's APDU commands documentation and compare it with the standard. I'm working in a example of this procedure here[2]. Best regards!! [1] https://github.com/OpenSC/OpenSC/blob/master/src/libopensc/iso7816.c [2] https://github.com/alediator/OpenSC/tree/1_add_base_support Alejandro Díaz Torres Área de Proyectos Emergya Consultoría Tfno: +34 954 51 75 77 Fax: +34 954 51 64 73www.emergya.es
_______________________________________________ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
