C. Ruiz, Ivan wrote:
>The problem is clearly on OpenSC pkcs#11 implementation, but with the
option --pkcs11-sign-mode
> you have included we can workarround it!
OK... So we can close this issue.
> I agree to drop support for OpenSC. The PKCS#11 approach works well with
OpenSC and it will
> broad
0
Para: openvpn-devel@lists.sourceforge.net
Asunto: [Openvpn-devel] openvpn - support PKCS#11 smartcards
Hello,
C. Ruiz, Ivan wrote:
>
> I only changed C_SignRecover to C_Sign and C_SignRecoverInit to C_SignInit
> (pkcs11.c) and
> it worked for me with OpenSC. Can you test if it
Hello,
C. Ruiz, Ivan wrote:
I only changed C_SignRecover to C_Sign and C_SignRecoverInit to C_SignInit (pkcs11.c) and
it worked for me with OpenSC. Can you test if it's OK for you with this minor
change?
Hmmm... It should be SignRecover... strange they don't support
it... Anyway, please
27;t have the compiler for this
platform.
Regards,
Iván Casado Ruiz
SADIEL, S.A.
-Mensaje original-
De: C. Ruiz, Ivan
Enviado el: lunes, 12 de septiembre de 2005 9:19
Para: openvpn-devel@lists.sourceforge.net
CC: 'Alon Bar-Lev'
Asunto: RE: [Openvpn-devel] openvpn - support PKC
ad...@lists.sourceforge.net]En nombre de Alon
Bar-Lev
Enviado el: sábado, 10 de septiembre de 2005 23:17
Para: openvpn-devel@lists.sourceforge.net; Avner Peled;
zv...@globalnet.hr
Asunto: [Openvpn-devel] openvpn - support PKCS#11 smartcards
Hello,
There are two widely used standards of accessing crypto
Hello,
There are two widely used standards of accessing cryptographic
devices: RSA Security Inc PKCS#11 and Microsoft Cryptographic
Service Provider.
Currently openssl has a Microsoft CryptoAPI interface.
PKCS#11 is a cross platform vendor independed interface, which
is used by most smartca
