On 2011-08-14 08:59, Alon Bar-Lev wrote:
> There had been always unified API: PKCS#11.
> Well, at Microsoft environment there was CryptoAPI Provider.
> The good about the CryptoAPI is that it allowed enough flexibility so
> that, for example, you could have created a generic CryptoAPI provider
> on
> PKCS#15 card producers resolve this problem by
> creating parallel CSP file system, invisible for PKCS#15,
> or by creating 'DATA' objects with the common 'application' attribute,
> for ex. "BaseCSP".
>
> I guess that this second approach is more appropriate for the OpenSC
> minidriver.
>
> The
Hello,
On Sun, Aug 14, 2011 at 13:21, Dhinesh gunasekaran
wrote:
> hi,
>
> i tried creating a certificate after loading pkcs11 engine and module
> opensc-pkcs11.so, i get the following errors,
>
> Organizational Unit Name (eg, section) []:testbed
> Common Name (eg, YOUR name) [CA_dhinu]:CA_dhinu
hi,
i tried creating a certificate after loading pkcs11 engine and module
opensc-pkcs11.so, i get the following errors,
Organizational Unit Name (eg, section) []:testbed
Common Name (eg, YOUR name) [CA_dhinu]:CA_dhinu
Email Address [d.gunaseka...@gmail.com]:d.gunaseka...@gmail.com
problems making
There had been always unified API: PKCS#11.
Well, at Microsoft environment there was CryptoAPI Provider.
The good about the CryptoAPI is that it allowed enough flexibility so
that, for example, you could have created a generic CryptoAPI provider
on-top of PKCS#11.
In the MiniDriver, Microsoft adva
