i have jcop v2.4.2 r3 java card. when insert in acr38 reader , send 2 consecutive atr request opensc-tool, receive 2 different atr! ok?
look:
commandline> osc.exe -a using reader card: acs ccid usb reader 0 3b:f0:13:00:00:81:31:fe:45:e8 commandline> osc.exe -a using reader card: acs ccid usb reader 0 3b:f9:13:00:00:81:31:fe:45:4a:43:4f:50:32:34:32:52:33:a2 if repeat request without delay, receive second atr again , again :
commandline> osc.exe -a using reader card: acs ccid usb reader 0 3b:f9:13:00:00:81:31:fe:45:4a:43:4f:50:32:34:32:52:33:a2 commandline> osc.exe -a using reader card: acs ccid usb reader 0 3b:f9:13:00:00:81:31:fe:45:4a:43:4f:50:32:34:32:52:33:a2 commandline> osc.exe -a using reader card: acs ccid usb reader 0 3b:f9:13:00:00:81:31:fe:45:4a:43:4f:50:32:34:32:52:33:a2 but if wait 1 minutes (and don't remove card reader), , request atr again, receive first short atr :
commandline> osc.exe -a using reader card: acs ccid usb reader 0 3b:f9:13:00:00:81:31:fe:45:4a:43:4f:50:32:34:32:52:33:a2 // waiting 1 minutes while card inserted in reader. commandline> osc.exe -a using reader card: acs ccid usb reader 0 3b:f0:13:00:00:81:31:fe:45:e8 //requesting atr again , without delay. commandline> osc.exe -a using reader card: acs ccid usb reader 0 3b:f9:13:00:00:81:31:fe:45:4a:43:4f:50:32:34:32:52:33:a2
without mentioned reader best guess is, experience difference between cold reset , warm reset, see iso 7816-3.
but since difference is, in short version no historical bytes provided , in long 9 historical bytes indicate "jcop242r3", surely of minor importance.
Comments
Post a Comment