On Friday 14 April 2006 23:28, Chaskiel M Grundman wrote: > Two patches are attached. One is what I've been running for most of today. > it successfully resets and can do some communication with ITSEC-P/2048/5 > devices. > > The second implements Justin's suggestion that we just ignore TA(0) in the > ATR, not negotiate higher speed serial communication with PTS, and use 01 > as the parameter when configuring the baud rate of the 'reader' (in the > 0x65 request) This version seems to behave no worse with the ITSEC-P, and > does not seem to bother the ITSEC-I either. If it fixes the problems with > the FIPS model, it may be the right way to go
Ok I tried the second patch (eutron2.diff). Fetching the ATR and serial number works on the ITSEC-P. Fetching the ATR on the FIPS does not work the first try after insert, but it works on subsequent tries (I guess you didn't roll in support for skipping the zero byte?). Fetching the serial number does not work either, because I think opensc doesn't recognize the FIPS model as a supported card. Adding its ATR into card-starcos.c's table allows me to get the serial number. If you think it should be added, here's the ATR: 3b:b7:18:00:c0:3e:31:fe:65:53:50:4b:32:34:90:00:25 The ATR of the ITSEC-P model seems to already be in the table, so I didn't have to worry about that one. I tried running: pkcs11-tool --module /usr/local/lib/opensc-pkcs11.so --show-info But this fails for both of my cards, so it seems nothing works yet (not that you intended for anything to work yet, but I wasn't sure). I wonder, does the ITSEC-I model work for you? Eutron's web page claims that OpenSC supports this model, which I would hope means more than just fetching the ATR and serial number. :) -Justin _______________________________________________ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
