>ok. so we would need a pkcs#11 to Crypto api bridge,
>so pkcs#11 api applications can use the certificates available
>via crypto api.
Oh yes, think it's good idea, I've not see this possibility. In this case
getting a statically build of libopensc maybe interesting...
>trunk is under development, and I guess it will be for a while.
>so we can add your patches whenever you want. since the feature
>can be turned on/off via configure flags, there is no harm to
>add the code early, even if it is still under development.
Very good, so code can be added early and everybody will can improve it...
>simply let me know when you think the code could be added and
Ok, I let me do some cleaning first and see to integrate it.
>I will commit it (or you can have access to svn and commit it
>yourself).
I can do this myself?
Regards
François
_______________________________________________
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel
