Subject: Aladdin eToken Pro - msg#00099

Previous Message by Date: click to view message preview

Re: Definition of APDU standard? What's ISO T=0? [u]

At Thu, 21 Jul 2005 10:29:25 +0200, Andreas Jellinghaus [c] wrote: > there are a dozen or so transmission protocolls. the only important > ones are T=0 (byte by byte) and T=1 (block) and the wireless ones. > > standard APDU are in iso7816.c and iso 7816 part 4 to 9 (or whatever > the latest part is). Usualy noone implements them except part 4 (the > other parts were defined quite late). > > and even if the command is standard, the data structure used or the > response might not. Thank you very much. This is valuable background information. > opensc.org has a resources web page with links. google might help as > well finding copies of that standard. Oups - sorry, I missed that page. -- Felix E. Klee

Next Message by Date: click to view message preview

Re: Aladdin eToken Pro [u]

what about cardos-info? > "Card ATR: 3B E2 00 FF C1 10 31 FE 55 C8 02 9C ;.....1.U..." cardos 4.0. maybe it is missing some "packages" for example with "ls" command etc.? to solve that, please format it with the windows tools. unless those apps install "packages" the card could be missing several important commands. > # opensc-tool -f (turns off the red led) > card.c:203:sc_transceive: Unable to transmit: Generic reader error strange. generic reader error shouldn't happen. but maybe this is a strange way of telling us that it doesn't understand some command? openct debug level 6 and a syslog excerps (ifdhandler lines) could help to show what is wrong. Regards, Andreas

Previous Message by Thread: click to view message preview

KOBIL Kaan Professional and OpenSC

Hi, I am just sitting in front of of a brand new Kobil Kaan Professional, trying to activate my Telesec smartcard. Unfortunately, without success, I cannot access the card. Kobil has provided a CT-API driver for the reader, so I opensc.conf looks like app default { reader_drivers = ctapi; reader_driver ctapi { module /usr/lib/libct.so { ports = 1; } } } where /usr/lib/libct.so is the Kobil driver. Now I wanted to use opensc-explorer to show some information about my smartcard with the following result: mithrandir:~ # opensc-explorer -vvv OpenSC Explorer version 0.9.4 sc.c:120:sc_detect_card_presence: called sc.c:125:sc_detect_card_presence: returning with: 0 Card not present. ctx.c:602:sc_release_context: called Why does not it detect my card? The card IS present. I turned on debugging of the Kobil driver and here is its output: /* DLL_PROCESS_ATTACH by /lib/libdl.so.2 at 13:27:00 987 ms */ CT_INIT(0, 1) // at 13:27:00 987 ms Initialized Mutex for port 1 (ctn 0) /* Open Serial Port /dev/ttyUSB0 at 13:27:00 988 ms */ /* SetParameter /dev/ttyUSB0:13,,8,1 (CWT=500)*/ < (0) // OK CT_DATA(0, 1,2) [5] 20 13 00 80 00 // at 13:27:00 991 ms /* SetParameter /dev/ttyUSB0:13,,8,1 (CWT=200)*/ /* Hardware Reset ( Discarding: 00 ffffff80 ffffff80 ffffff80 00 00 00 ffffff80 ffffff80 ffffff80 00 ffffff80 00 00 00 ffffff80 00 ffffff80 00 ffffff80 00 ffffff80 ffffff80 00 ffffff80 00 ffffff80 00 ffffff80 ffffff80 00 ffffff80 ffffff80 ffffff80 ffffff80 ffffff80 00 00 00 00 ffffff80 ffffff80 00 ffffff80 00 00 00 00 00 00 00 ffffff80 ffffff80 ffffff80 00 ffffff80 00 00 00 ffffff80 ffffff80 00 00 00 00 ffffff80 00 ffffff80 00 ffffff80 ffffff80 ffffff80 00 ffffff80 00 00 00 ffffff80 00 00 00 00 00 ffffff80 ffffff80 ffffff80 00 ffffff80 00 ffffff80 00 00 00 00 ffffff80 00 ffffff80 00 00 ffffff80 ) ( Discarding: ffffff80 00 ffffff80 00 ffffff80 ffffff80 00 00 ffffff80 00 ffffff80 ffffff80 00 ffffff80 ffffff80 00 ffffff80 ffffff80 00 ffffff80 00 00 ffffff80 00 00 ffffff80 ffffff80 00 ffffff80 ffffff80 ) ( No more data to discard ) ( Discarding: 00 ffffff80 ffffff80 ffffff80 00 00 00 ffffff80 ffffff80 ffffff80 00 ffffff80 00 00 00 ffffff80 00 ffffff80 00 ffffff80 00 ffffff80 ffffff80 00 ffffff80 00 ffffff80 00 ffffff80 ffffff80 00 ffffff80 ffffff80 ffffff80 ffffff80 ffffff80 00 00 00 00 ffffff80 ffffff80 00 ffffff80 00 00 00 00 00 00 00 ffffff80 ffffff80 ffffff80 00 ffffff80 00 00 00 ffffff80 ffffff80 00 00 00 00 ffffff80 00 ffffff80 00 ffffff80 ffffff80 ffffff80 00 ffffff80 00 00 00 ffffff80 00 00 00 00 00 ffffff80 ffffff80 ffffff80 00 ffffff80 00 ffffff80 00 00 00 00 ffffff80 00 ffffff80 00 00 ffffff80 ) ( Discarding: ffffff80 00 ffffff80 00 ffffff80 ffffff80 00 00 ffffff80 00 ffffff80 ffffff80 00 ffffff80 ffffff80 00 ffffff80 ffffff80 00 ffffff80 00 00 ffffff80 00 00 ffffff80 ffffff80 00 ffffff80 ffffff80 ) ( No more data to discard ) - OK */ ( No more data to discard ) > 00 c0 00 c0 at 1832 ms < 00 e0 00 at 1861 ms < e0 at 1861 ms Locked Mutex for port 1 (ctn 0) ( No more data to discard ) > 12 00 05 20 13 00 80 00 a4 at 1918 ms < 21 00 05 at 1941 ms < 80 01 03 90 00 36 at 1949 ms Unlocked Mutex for port 1 (ctn 0)< (0) [5] 80 01 03 90 00 // at 13:27:02 940 ms CT_DATA(0, 1,2) [5] 20 13 00 80 00 // at 13:27:02 940 ms Locked Mutex for port 1 (ctn 0) ( No more data to discard ) > 12 40 05 20 13 00 80 00 e4 at 57 ms < 21 40 05 at 80 ms < 80 01 03 90 00 76 at 88 ms Unlocked Mutex for port 1 (ctn 0)< (0) [5] 80 01 03 90 00 // at 13:27:03 028 ms CT_CLOSE(0) // at 13:27:03 028 ms ( No more data to discard ) /* Close Port at 75 ms */ < (0) // OK So, where is the problem? Thanks, Tilman

Next Message by Thread: click to view message preview

Re: Aladdin eToken Pro [u]

what about cardos-info? > "Card ATR: 3B E2 00 FF C1 10 31 FE 55 C8 02 9C ;.....1.U..." cardos 4.0. maybe it is missing some "packages" for example with "ls" command etc.? to solve that, please format it with the windows tools. unless those apps install "packages" the card could be missing several important commands. > # opensc-tool -f (turns off the red led) > card.c:203:sc_transceive: Unable to transmit: Generic reader error strange. generic reader error shouldn't happen. but maybe this is a strange way of telling us that it doesn't understand some command? openct debug level 6 and a syslog excerps (ifdhandler lines) could help to show what is wrong. Regards, Andreas