Re: [opensc-devel] SC_ASN1_SEQUENCE not managed by asn1_decode_entry()?

Ludovic Rousseau wrote: Hello, the seInfo field is defined in libopensc/pkcs15.c as: { "seInfo", SC_ASN1_SEQUENCE, SC_ASN1_CONS | SC_ASN1_TAG_SEQUENCE, SC_ASN1_OPTIONAL, NULL, NULL }, but SC_ASN1_SEQUENCE type is not managed by asn1_decode_entry() in libopensc/asn1.c this is not rea

Re: [opensc-devel] tokenInfo serialNumber is no more mandatory in ISO 7816-15 but was in PKCS#15

Ludovic Rousseau wrote: Hello, I have a card conforming to ISO 7816-15. ISO 7816-15 is slightly different from PKCS#15 and among other changes the tokenInfo changed. In PKCS#15 (v1.1, June 2000, page 48) we have: TokenInfo ::= SEQUENCE { version INTEGER {v1(0)} (v1,...), s

[opensc-devel] SC_ASN1_SEQUENCE not managed by asn1_decode_entry()?

Hello, the seInfo field is defined in libopensc/pkcs15.c as: { "seInfo", SC_ASN1_SEQUENCE, SC_ASN1_CONS | SC_ASN1_TAG_SEQUENCE, SC_ASN1_OPTIONAL, NULL, NULL }, but SC_ASN1_SEQUENCE type is not managed by asn1_decode_entry() in libopensc/asn1.c I guess nothing bad happens if the field

[opensc-devel] tokenInfo serialNumber is no more mandatory in ISO 7816-15 but was in PKCS#15

Hello, I have a card conforming to ISO 7816-15. ISO 7816-15 is slightly different from PKCS#15 and among other changes the tokenInfo changed. In PKCS#15 (v1.1, June 2000, page 48) we have: TokenInfo ::= SEQUENCE { version INTEGER {v1(0)} (v1,...), serialNumber OCTET ST