>> I would like to kindly ask you for a few clarifications on this : >> 1) Which protocol is used then for communication with this card >> (looking at presented ATR) ? T=0 ? > >Used by who? >pcsc-lite uses T=0 by default unless the card declares (in the ATR) it >supports T=1.
ISO says that if no protocol is given by the ATR, you shall assume that the card uses T=0. In your case, T=0 is given, so it should be clear :) >> 3) For my curiosity, do you have any idea why is this T=15 appearing ? > >No. T=15 is supposed to be reserved for future use (as per ISO-7816-3.1.a). In practice, you should treat it as T=0. >> 4) Should we always quietly ignore any other TDi character apart from >> one that gives us T=0 or T=1 ? > >It depends on what you want to do. I suggest you give a look to the Smartcard Handbook (http://www.amazon.com/Smart-Card-Handbook-Wolfgang-Rankl/dp/0470856688/ref=dp_ob_title_bk), in particular chapter 6. It's a bit pricey but it's a very good book (saved me tons of time when I had to understand all that smartcard fluff :)). http://www.smartcard.co.uk/tutorials/sct-itsc.pdf also have information on the content of the ATR. Most of the time, the ATR is important to the reader device and to the device driver, as it gives hints on how to initialize the connection between the card and the PC. If you work at application level, it can also give you information on how you can configure the smartcard for specific use (this is kind of useful for double-reset cards). But unless you want to do something very specific, parsing the ATR is of no interest at application level. Now, at the driver/device/card level, it's a completely different thing: the ATR gives you many information on how to set up the connection (including the communication speed, timeout duration and so on). If this is your goal, you'd better read either the ISO standard or the Smartcard handbook - they'll prove to be invaluable resources. Best regards, -- Emmanuel Deloget -- ------------------------------------------------ Emmanuel Deloget [[email protected]] Software Project Manager @ Amesys Conseil +33 (0)6 24 195 448 _______________________________________________ Muscle mailing list [email protected] http://lists.drizzle.com/mailman/listinfo/muscle
