Doug Engert

> Since you are the first one noticing this after three years, I do not think anyone heavily depended on this functionality. I would look at it as a regression....

As far as I can tell, many people turn to OpenSC when they have a card (usually issued by their government) that works on windows but the issuer does not...

You are correct. The ISO 7816-4 verify command should also return 63 CX for an incorrect pin. The YubiKey 5 NFC says it implements PGP version 3.4. ``` ./openpgp-tool -C...

V3.4.1 says verify can check status. V2.sometbing does not. On Sat, Jun 11, 2022, 8:33 AM MkfsSion ***@***.***> wrote: > > - You're talking about the PGP application of the...

Will look at this later today.

I see two problems. First is the input data has the first tag length wrong. It is missing a extra "81" Current opensc can not parse the template if more...

I also see they are using the tag AC, which is new in NIST sp800-74-4 defines in Table 5. Which say before it: " A PIV Card Application may use...

If the tag lengths are correct the parsing works at https://github.com/OpenSC/OpenSC/blob/f1691fc91fc113191c3a8aaf5facd6983334ec47/src/libopensc/card-piv.c#L778 Then code finds the response looks like a PIV card because the response has the AID and returns from...

https://github.com/OpenSC/OpenSC/pull/2053 fixes these problems as part of a major rewrite of card-piv.c. It will read up to SC_MAX_APDU_BUFFER_SIZE, and uses sc_asn1_find_tag to parse the response.

The tests so far have shown that the CCID driver is working fine. So adding it to supported_readers.txt is not needed. "Failed to connect to card: Card is invalid or...