Hello Victor,
Im playing with opensc and find that when we use pkcs15 emulation
sc_pkcs15_verify_pin fails,
this is due to 'auth_method' not set by emulation layer (and use to be set
by 'sc_pkcs15_verify_pin'
before changeset 4048). For real pkcs15 card it seems that
François Leblanc wrote:
Hello Victor,
I’m playing with opensc and find that when we use pkcs15 emulation
sc_pkcs15_verify_pin fails,
this is due to 'auth_method' not set by emulation layer (and use to be set
by 'sc_pkcs15_verify_pin'
before changeset 4048). For real pkcs15 card it seems
On Feb 23, 2010, at 12:39 , Viktor TARASOV wrote:
François Leblanc wrote:
Hello Victor,
I’m playing with opensc and find that when we use pkcs15 emulation
sc_pkcs15_verify_pin fails,
this is due to 'auth_method' not set by emulation layer (and use to be set
by 'sc_pkcs15_verify_pin'
Martin Paljak wrote:
On Feb 23, 2010, at 12:39 , Viktor TARASOV wrote:
François Leblanc wrote:
Hello Victor,
I’m playing with opensc and find that when we use pkcs15 emulation
sc_pkcs15_verify_pin fails,
this is due to 'auth_method' not set by emulation layer (and use to be set
Ok so Can I apply joined patch? Tested only with Westcos Card...
Hope I forget nobody...
No objections?
François.
emulation-set-auth-method.patch
Description: Binary data
smime.p7s
Description: S/MIME cryptographic signature
___
opensc-devel
On Feb 23, 2010, at 14:18 , Viktor TARASOV wrote:
Maybe, for the first one the specially dedicated macros should be defined.
First what? Please explain.
In fact, by definition, the authentication method of the AUTH PKCS#15
object cannot be SC_AC_NONE (method 'not none' is it's reason for
François Leblanc wrote:
Ok so Can I apply joined patch? Tested only with Westcos Card...
As for me, 'yes, you can'.
Later, probably, we will introduce specially dedicated macros for the
PIN auth. method values .
François.
On Feb 23, 2010, at 14:40 , François Leblanc wrote:
No objections?
Yes.
The wrappers in pcks15-syn.c are supposed to simplify the creation of PKCS#15
emulation drivers.
Until other than PIN authentication is implemented, it is safe to say that the
_add_pin_object wrapper can set the auth
Martin Paljak wrote:
On Feb 23, 2010, at 14:18 , Viktor TARASOV wrote:
Maybe, for the first one the specially dedicated macros should be defined.
First what? Please explain.
I mean the macros for the possible values of AUTH object authentication
method.
In fact, by
Index: pkcs15-syn.c
===
--- pkcs15-syn.c (revision 4063)
+++ pkcs15-syn.c (working copy)
@@ -316,6 +316,8 @@
sc_pkcs15_pin_info_t pin = *in_pin;
pin.magic = SC_PKCS15_PIN_MAGIC;
+ if
François Leblanc wrote:
Index: pkcs15-syn.c
===
--- pkcs15-syn.c (revision 4063)
+++ pkcs15-syn.c (working copy)
@@ -316,6 +316,8 @@
sc_pkcs15_pin_info_t pin = *in_pin;
pin.magic = SC_PKCS15_PIN_MAGIC;
+
11 matches
Mail list logo
