Re: ACR122U response frames contain wrong sequence numbers

Hello

for your information, no ACR122 reader ever worked OK with any card I 
tested (types A and B).
Both under linux and windows.
At this time I could not investigate deeply, so we changed the readers 
and never got any problems with the same cards :)

So I don't exactly know the cause, but you're not alone having problems 
with this reader :)

Sebastien Lorquet


Le 18/08/2013 12:05, Eugene Crosser a écrit :
> A little followup:
>
> On 08/16/2013 03:15 PM, Eugene Crosser wrote:
>
>> I've got ACR122U reader and noticed that when a CCID frame sent from the
>> host to the token is larger than 64 bytes (APDU larger than 54 bytes),
>              of the response frame
>              ---------v-----------
>> the sequence number (byte at +6 in the CCID frame) is one less than the
>> sequence number of the sent frame.
>   ...
>
>> I must note that openpgp functionality works over this reader (maybe
>> they never use APDUs bigger than 54 bytes?).
> I checked and indeed, they do not:
>
> $ grep CmdXfrBlockTPDU /var/tmp/gpg-ccid-log.txt
> 00000013 commands.c:1619:CmdXfrBlockTPDU_T0() T=0: 11 bytes
> 00000006 commands.c:1619:CmdXfrBlockTPDU_T0() T=0: 5 bytes
> 00000005 commands.c:1619:CmdXfrBlockTPDU_T0() T=0: 5 bytes
> 00000005 commands.c:1619:CmdXfrBlockTPDU_T0() T=0: 5 bytes
> 00000006 commands.c:1619:CmdXfrBlockTPDU_T0() T=0: 5 bytes
> 00000006 commands.c:1619:CmdXfrBlockTPDU_T0() T=0: 5 bytes
> 00000007 commands.c:1619:CmdXfrBlockTPDU_T0() T=0: 5 bytes
> 00000006 commands.c:1619:CmdXfrBlockTPDU_T0() T=0: 5 bytes
> 00000006 commands.c:1619:CmdXfrBlockTPDU_T0() T=0: 5 bytes
> 00000002 commands.c:1619:CmdXfrBlockTPDU_T0() T=0: 5 bytes
> 00000007 commands.c:1619:CmdXfrBlockTPDU_T0() T=0: 5 bytes
> 00000006 commands.c:1619:CmdXfrBlockTPDU_T0() T=0: 11 bytes
> 00000006 commands.c:1619:CmdXfrBlockTPDU_T0() T=0: 41 bytes
> 00000005 commands.c:1619:CmdXfrBlockTPDU_T0() T=0: 5 bytes
>
> This is going to be a real problem if/when yubikey's library gets the
> functionality of reaching the key over PC/SC. In challenge-response mode, they
> are sending frames longer than 54 bytes, and it works over the yubikey's
> built-in CCID implementation, but not over the ACR reader.
>
> Anybody?
>
> Regards,
>
> Eugene
>
>
>
> _______________________________________________
> Muscle mailing list
> [email protected]
> http://lists.musclecard.com/mailman/listinfo/muscle_lists.musclecard.com

_______________________________________________
Muscle mailing list
[email protected]
http://lists.musclecard.com/mailman/listinfo/muscle_lists.musclecard.com