Hello,
I have been trying to make my Litronic 210 and Open16K card to work
for several weeks with not much success.
I have used the ct-api driver for Litronic 210 (the docs say about
the Litronic Argus 210, my reader does not say Argus anywhere).
XCard-ctapi, when it runs, it gives an error at the Iso_Reset function.
(I will bring tomorow more details.).
When I use the "reader" example program from the litronic ctapi package,
and issue the commands, I get:
(I have logged the commands from the ToolKit application for Windows
and spefically the commands to "Select" the application on the smartcard
to make it run. I want to run the Wallet example from Cyberflex Open16).
Script started on Fri Jan 8 14:35:21 1999
# ./reader-modified
Successful
Initialize
Successful Reset/Set Mode
ATR Response Size: 09
3b 16 94 81 10
05 00 00 51
Card inserted.
APDU: 0040000000 // Validate
command from Wallet.java
APDU to send: 00 40 00 00 00
Command sent
successfully:
00 40 00 00 00
Response:
6d 00
// Ok, does not work since Wallet is not active yet.
APDU:
A0A404000700000000000077
APDU to send: a0 a4 04 00 07 00 00 00 00 00 00 77
Command sent successfully:
a0 a4 04 00 07 00 00 00 00 00 00 77
Response:
9f 28 // What is this?
APDU: A0F2000028
APDU to
send: a0 f2 00 00 28
Command sent successfully:
a0 f2 00 00 28
Response:
67 17 // Needs 17
// Up to here, everything is
ok. The next command returns a BYTE[] that
// starts with "f2". The
"Toolkit" application does not return such a byte.
//
APDU: A0F2000017
APDU
to send: a0 f2 00 00 17
Command sent successfully:
a0 f2 00 00 17
Response:
f2 00 00 00 62 69 69 02 3f 00 02 14 03 1b 13 00 02 00 00 00 00
00 00 00 90 00
00 00 00 62 69 69 02 3F 00 02 14 03 1B 13 00 02 00 00 00
00 00 00 00
// Just above line is from ToolKit log window. Why do I receive
that "f2" from
// litronic-ctapi-0.0.1?
// After this, all the other
fail!
// 90 00 is returned on a separate line in the ToolKit. How does it
know?
// Are two lines of bytes, two packets given?
APDU:
A0A40000026969
APDU to send: a0 a4 00 00 02 69 69
Command sent
successfully:
a0 a4 00 00 02 69 69
Response:
9f 28
APDU:
F0A8000128
APDU to send: f0 a8 00 01 28
Command sent successfully:
f0 a8
00 01 28
Response:
a8 69 69 03 22 22 22 04 00 00 00 00 01 01 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 90 00
APDU: F0A8000228
APDU to send: f0 a8 00 02 28
Command sent successfully:
f0 a8 00 02 28
Response:
a8 69 69 00 70 22 23 04 00 ff ff 00 ff ff 01 01
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 90 00
APDU: 0040000000
APDU to send: 00 40 00 00 00
Command sent
successfully:
00 40 00 00 00
Response:
APDU: quit
Successful Eject
#
exit
Script done on Fri Jan 8 14:36:15 1999
The question are in the above "script" listing.
Thanks,
Simos Xenitellis
***************************************************************
Linux Smart Card Developers - M.U.S.C.L.E.
(Movement for the Use of Smart Cards in a Linux Environment)
http://www.linuxnet.com/smartcard/index.html
***************************************************************
