I am trying to debug an issue with the SCM 311 reader and Oberthur ID One card in order to better support Macs and smart card-enabled sites. I've been using pkcs15-tool to list certificates on the card. The result is that on the first run with the card inserted for the first time, certificates are listed. On the next, second run, no certificates are listed; pkcs15-tool reports no certificates.
Turning up the debugging volume, I get the following unified diff output (/tmp/run-11 is the first run, /tmp/run-22 is the second run, timestamps stripped). On the first run, the card is detected as a T0 protocol card. On the second run, the card is detected as a T1 protocol card. I'm fairly certain this is a problem (listing certificates requires APDU messages, not TPDU messages, no?), but not sure where to go look in the code to propose a patch. (*) --- /tmp/run-11 2012-09-05 10:12:04.000000000 -0700 +++ /tmp/run-22 2012-09-05 10:12:08.000000000 -0700 @@ -21,7 +21,7 @@ reader-pcsc.c:325:refresh_attributes: current state: 0x00000120 reader-pcsc.c:326:refresh_attributes: previous state: 0x00000120 reader-pcsc.c:380:refresh_attributes: card present -reader-pcsc.c:497:pcsc_connect: Initial protocol: T0 protocol +reader-pcsc.c:497:pcsc_connect: Initial protocol: T1 protocol card.c:868:match_atr_table: ATR : 3b:db:96:00:80:1f:03:00:31:c0:64:b0:f3:10:00:07:90:00:80 card.c:879:match_atr_table: ATR try : 3B:DD:18:00:81:31:FE:45:80:F9:A0:00:00:00:77:01:00:70:0A:90:00:8B card.c:882:match_atr_table: ignored - wrong length Leading up to this difference, both files have the same lines (again, timestamps stripped): sc.c:195:sc_detect_card_presence: called reader-pcsc.c:388:pcsc_detect_card_presence: called reader-pcsc.c:301:refresh_attributes: SCM SCR 331 00 00 check reader-pcsc.c:325:refresh_attributes: current state: 0x00000120 reader-pcsc.c:326:refresh_attributes: previous state: 0x00000122 reader-pcsc.c:380:refresh_attributes: card present reader-pcsc.c:393:pcsc_detect_card_presence: returning with: 5 sc.c:200:sc_detect_card_presence: returning with: 5 Using reader with a card: SCM SCR 331 00 00 sc.c:195:sc_detect_card_presence: called reader-pcsc.c:388:pcsc_detect_card_presence: called reader-pcsc.c:301:refresh_attributes: SCM SCR 331 00 00 check reader-pcsc.c:325:refresh_attributes: current state: 0x00000120 reader-pcsc.c:326:refresh_attributes: previous state: 0x00000120 reader-pcsc.c:380:refresh_attributes: card present reader-pcsc.c:393:pcsc_detect_card_presence: returning with: 5 sc.c:200:sc_detect_card_presence: returning with: 5 card.c:125:sc_connect_card: called reader-pcsc.c:468:pcsc_connect: called reader-pcsc.c:301:refresh_attributes: SCM SCR 331 00 00 check Any clues? -scooter (*) Would it be permissible to mark unused parameters in static functions as unused? Really. It gets in the way of tracking down interesting problems, like signed/unsigned conversions, integer length issues, ... If the code has to compile with -Wall, then the code could be selective with respect to which are really important warnings, no? _______________________________________________ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
