2011/8/25 Martin Paljak <mar...@martinpaljak.net>: > Hello, > > On Thu, Aug 25, 2011 at 14:47, Ludovic Rousseau > <ludovic.rouss...@gmail.com> wrote: >> The realy strange situation is that you can have a working T=0 >> card+reader with these "invalid" INS bytes. >> >> In your INS exploration program just skip 6X and 9X INS values. > > Thanks for the explanation! > > For the fun of it I think I'll do the opposite instead: > - make the protocol dependant probing more explicit (for several > stupid reasons I'm using T=0 only currently, as this is the only > "supported algorithm" for Estonian eID cards) > - DO probe the forbidden ranges (not by default though) > - see what happens with different card+reader combos :) > > Would it make sense to debug on USB level what is happening at > different situations, to maybe make the CCID driver more robust (== > predictable outcome with different readers)?
You can activate the communication logs in the CCID driver. But you will not see much more than at the PC/SC level. The error comes from the reader (I guess), not the CCID driver. The best would be to log at the card/reader interface. I guess the CardMan reader do not even try to send the "bogus" APDU to the card and just reject it. bye -- Dr. Ludovic Rousseau _______________________________________________ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
