On Thursday 16 March 2006 18:25, Justin Karneges wrote: > # opensc-tool --atr [snip] > Failed to connect to card: Card is invalid or cannot be handled > > Seems definitely broken still.
Follow-up: With some more debug, I can see that opensc is trying to write 5 bytes: 00 c0 00 00 00 It then attempts to get a response, I think. The first read returns 0 (no data?) then a second read returns -5 (IFD_ERROR_COMM_ERROR). This error comes from sys-linux.c as a result of the ioctl(). I don't know why we'd be getting a subsystem error here. Then opensc tries the same thing with these 5 bytes: 00 a4 00 00 02 In other words: sends, reads no data, reads error. After this second error happens, the command ends. > the first attempt at initialization after this modification, the ATR ended > up being 18 bytes (same ATR as before, but with a 0 byte prepended). > Further attempts show the normal 17 byte ATR. I don't know if this is > related to the modification yet, I'll have to try more times. Maybe the > serial stream was off-by-one as a fluke. I noticed this occurs every once in awhile and doesn't seem related to any of the changes so far. It's even in that usb snoop log. > > safesign sent a different PTS sequence (I don't have time to decode it > > now. sorry) > > Can you give me a line number in the log so I can try? I'm still not sure > how to read this thing. Is it: ff 11 14 fa ? I tried setting this as the new cookie data, but it didn't have any apparent effect. Another question: Does it matter that all the windows USB writes begin with 42? In the openct driver, the init writes begin with 41, and the "normal" writes begin with 42. I tried changing the opensc driver to use 42 all the time, but again to no apparent effect. -Justin _______________________________________________ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
