Hi Andreas and François and everybody!

Thank you for your quick response. I have already initialized the card, this 
one have no pkcs15 structure, but I can create a few EFs into a DF. I think 
that I can implement a file system into a large EF and I will use it to store 
all pkcs15 structure. This option can be dangerous in security ways, because I 
must to set read only access to this EF that contains the filesystem and a 
person can do an image from my filesystem and compromise it.

I made several changes to pkcs15-syn in order to register the new driver. I 
added to opensc in builtin mode in a linux system.

I have a filesystem coded in C++, can I use it with opensc? Could be any 
problem with this change ? I have seen that opensc is coded in C, can I change 
Makefile from gcc to g++?

Thank you very much, regards.

--- El mar, 12/5/09, Andreas Jellinghaus <a...@dungeon.inka.de> escribió:

> De: Andreas Jellinghaus <a...@dungeon.inka.de>
> Asunto: Re: [opensc-devel] Testing a new driver - File not found
> Para: "Egon" <lista...@yahoo.es>
> CC: opensc-devel@lists.opensc-project.org
> Fecha: martes, 12 mayo, 2009 11:39
> 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

Reply via email to