Sorry, I've done.

I've integreated "westcos" cards.

You need to implement a "card-xxx.c " a "pkcs15-xxx.c" and to create a 
tool "xxx-tool.c"

With westcos-tool I use opensc api to write file I need on the card, I 
use pkcs15-westcos.c to

emulate pkcs15 structure for this card and of course card-westcos for 
interface betwin opensc and westcos card.

It is not so hard, but be careful I've started integrating this in 
librairies (under windows) and this not work with vista

due to memory management (all malloc, calloc must be free in same 
process and opensc don't care of this).

I put my work like internal card module and build completly opensc 
(cross compiling under linux) and it seem to work.

For now I try to get avaibility to build on windows with virtual 
linux... (I use qemu and a debian distribution)

The more difficult is to build completly opensc under linux with your 
code but if you are under linux it's quite easy.

So go and if you need some help...

Good luck.
François.

Andreas Jellinghaus a écrit :
> Hi Egon,
>
> so I get this right: you have a blank card, and you want to write
> a driver for it, so you can initialize that card, create PINs,
> create or store keys, store certificates and so on?
>
> but you don't want to implement PKCS#15, but some other format
> instead?
>
> I think you need to write a huge amout of code.
> the basic infrastructure should be already there:
> pkcs11 has a framework interface, and currently there is only
> a pkcs15init implementation. you can add an implementation
> of your own, and link it to your card driver.
>
> but note: noone has implemented something like this before,
> all the emulation drivers we have are read-only so far.
>
> good luck!
>
> Regards, Andreas
> _______________________________________________
> opensc-devel mailing list
> opensc-devel@lists.opensc-project.org
> http://www.opensc-project.org/mailman/listinfo/opensc-devel
>
>   
_______________________________________________
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel

Reply via email to