Hi, > Do any of the muscle drivers have a complete implementation > of T0: ie. it implements all the cases of TPDU2APDU, handling > the APDU result�fragmentation,��8613-4 appendix A > error exceptions etc?
The towitoko driver [1] claims that it handles : "direct and inverse convention cards, T=0 and T=1 protocols. Short and extended case 1, 2, 3, 4 ISO 7816-3 APDU's. PPS and baudrate selection from 9600 bps to 115200 bps." I have some problems with it if I wish to use it with differents readers in the same time. But with one reader I have no problem at communication protocol level. Often the protocol between the reader and the host is proprietary and T=0 & T= 1 are only between the reader and the smart card. This is a reason why there is not library implementing T=0 & T=1 in the Driver Developer Kit that developers may be used to easily implement a driver. It seems to me that OpenCT [2] has a such library. It may be interesting for you. [1] http://www.geocities.com/cprados/ [2] http://www.opensc.org/cgi-bin/cvsweb/openct/ Regards, Damien Sauveron ------------------------------------------------- This mail sent through IMP: http://horde.org/imp/ _______________________________________________ Muscle mailing list [EMAIL PROTECTED] http://lists.musclecard.com/mailman/listinfo/muscle
