Re: ACR122U response frames contain wrong sequence numbers
Eugene Crosser <[email protected]>
| Newsgroups | gmane.comp.lib.muscle |
|---|---|
| Message-ID | <[email protected]> |
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
signature.asc
(application/pgp-signature, 545 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iQEVAwUBUhCcZzy8vXtX5W5FAQKf7wgAgS6PNMDM9jpaXeXCHbBldzkw17YdWz2D HG91PBe5v2L4VPOumaNEqJ7sK0/fDdgXoS7RlNpsy8BVNIwH6QyQgZocTY4hWZII LlG5RYzZvcjJogNMrzoC/9GWvR77ZlSwE1TE8C4ky/5nCJRNSR9mHGWiVT4EMVjb quiWxqK46yYFuou1oNC+pe2TGGUzkc76DtNw08QBhLNYxGDvhuHlu/PHB+EF06le SJLPckCsrgS4D65dacorGhr3SoZ5lFfWDwedlEX3MNGklm0gT9oBMrEuRneEvwjy 1BXYys7/riPgCx2oN+YypDSEqZxwOsF+w3DqmzgqTK9ae0rS3Vty0A== =x4OO -----END PGP SIGNATURE-----