/[pcsclite]/trunk/Drivers/ccid/README
ViewVC logotype

Contents of /trunk/Drivers/ccid/README

Parent Directory Parent Directory | Revision Log Revision Log


Revision 1788 - (show annotations) (download)
Tue Jan 3 18:46:34 2006 UTC (7 years, 4 months ago) by rousseau
File size: 17321 byte(s)
add URL for SCM Micro SCR 3310
1 USB CCID IFD Handler
2 ====================
3
4 This package provides the source code for a generic USB CCID
5 (Chip/Smart Card Interface Devices) driver. See [1] for the USB CCID
6 specifications from the USB working group.
7
8
9 Authors:
10 ========
11
12 - Ludovic Rousseau <ludovic.rousseau@free.fr>
13 - Carlos Prados for the PPS and ATR parsing code (taken from his
14 towitoto driver) in towitoko/ directory.
15 - Olaf Kirch for the T=1 TPDU code (from the OpenCT package) in openct/
16 directory. I (Ludovic Rousseau) greatly improved this code.
17
18
19 Supported CCID readers:
20 =======================
21
22 (in alphabetical order)
23 - Advanced Card Systems ACR 38U-CCID [16]
24 old versions of this reader have a bug: the reader do timeout when a
25 special USB frame is sent from the reader. If the frame size if a
26 multiple of wMaxPacketSize the communication is stopped.
27 - Athena ASE IIIe USB V2 [29]
28 - Cherry XX33 keyboard [?]
29 - Cherry XX44 keyboard (SmartBoard G83-6744) [18]
30 - Cherry SmartTerminal ST2XXX
31 - Cherry ST-1044U [27]
32 - Dell keyboard SK-3106 [?]
33 - Dell smart card reader keyboard [?]
34 - Eutron SIM Pocket Combo [25]
35 - Eutron CryptoIdentity [26]
36 - Gemplus GemPC 433 SL [2]
37 - Gemplus GemPC Key [3]
38 - Gemplus GemPC Twin [4]
39 - Kobil KAAN Base [19]
40 - Kobil KAAN Advanced [20]
41 - Kobil KAAN SIM III [21]
42 - Kobil mIDentity [22]
43 - OmniKey CardMan 3121 [5]
44 - SCM Micro SCR 331 [6]
45 You shall upgrade the firmware [17] using version 5.18 or later.
46 - SCM Micro SCR 331-DI [11]
47 You shall upgrade the firmware [17] using version 6.22 or later.
48 - SCM Micro SCR 335 [7]
49 The firmware of this reader can't be upgraded so be sure to buy a
50 recent model with firmware 5.14 or later
51 - SCM Micro SCR 355
52 - SCM Micro SCR 3310 [30]
53 - SCM Micro SPR 532 [9]
54 You shall contact Torsten Maykranz <tmaykranz@scmmicro.de> to get a
55 firmware upgrade.
56 - Verisign Secure Storage Token [24]
57 - Verisign Secure Token [?]
58
59
60 Should work but untested by me:
61 ===============================
62
63 I would like to get these readers to perform test and validation and
64 move them in the supported list above. If you are one of the
65 manufacturers, please, contact me.
66
67 - ActivCard USB reader 2.0 [10]
68 - C3PO LTC32 [13]
69 - SCM Micro SCR 331-DI NTTCom [23]
70 - SCM Micro SCR 3310-NTTCOM [28]
71 - SCM Micro SCR 333 [15]
72 - Silitek SK-3105 keyboard [12] or C3PO TLTC2USB [14]
73
74
75 Unsupported or partly supported CCID readers:
76 =============================================
77
78 - C3PO LTC31 [8]
79 The reader works fine with Linux kernel 2.4 but does not with Linux
80 kernel 2.6. The ioctl() syscall returns EINVAL (Invalid argument)
81 - RSA SecureID SID800 [24]
82 The USB layer is completely broken. The reader is sometimes not even
83 seen on the USB bus (same problem under Windows). Maybe newer
84 devices will work?
85
86
87 Supported operating systems:
88 ============================
89
90 - GNU/Linux (libusb 0.1.7)
91 - MacOS X/Darwin (libusb 0.1.8beta, CVS snapshot. See "Known problems")
92 to libusb)
93
94
95 Debug informations:
96 ===================
97
98 The driver uses the debug function provided by pcscd. So if pcscd sends
99 its debug to stdout (pcscd --foreground) then the CCID will also send
100 its debug to stdout. If pcscd sends its debug to syslog (by default)
101 then the CCID will also send its debug to syslog.
102
103 You can change the debug level using the Info.plist configuraion file.
104 The Info.plist is installed, by default, in
105 /usr/local/pcsc/drivers/ifd-ccid.bundle/Contents/Info.plist
106
107 The debug level is set in the ifdLogLevel field. It is a binary OR
108 combinaison of 4 different levels.
109 - 1: critical: important error messages
110 - 2: info: informative messages like what reader was detected
111 - 4: periodic: periodic info when pcscd test if a card is present (every
112 1/10 of a second)
113 - 8: comm: a dump of all the bytes exchanged between the host and the
114 reader
115
116 By default the debug level is set to 3 (1 + 2) and correspond to the
117 critical and info levels.
118
119 You have to restart the driver so it read the configuration file again
120 and use the new debug level value. To restart the driver you just need
121 to unplug all your CCID readers so the the driver is unloaded and then
122 replug your readers. You can also restart pcscd.
123
124
125 Known problems:
126 ===============
127
128 MacOSX libusb
129 """""""""""""
130 There is a bug in libusb that crash the libusb library when you
131 unplug a reader and replug it in another USB socket. So if you
132 unplug a reader replug it in the same USB socket.
133
134 see http://sourceforge.net/tracker/index.php?func=detail&aid=886778&group_id=1674&atid=101674
135
136
137 Licence:
138 ========
139
140 This library is free software; you can redistribute it and/or modify it
141 under the terms of the GNU Lesser General Public License as published by
142 the Free Software Foundation; either version 2.1 of the License, or (at
143 your option) any later version.
144
145 This library is distributed in the hope that it will be useful, but
146 WITHOUT ANY WARRANTY; without even the implied warranty of
147 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Lesser
148 General Public License for more details.
149
150 You should have received a copy of the GNU Lesser General Public License
151 along with this library; if not, write to the Free Software Foundation,
152 Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
153
154
155 History:
156 ========
157
158 0.9.4 - 27 November 2005, Ludovic Rousseau
159 - add support for Eutron SIM Pocket Combo, Eutron CryptoIdentity,
160 Verisign Secure Token and VeriSign Secure Storage Token, GemPC
161 Card (PCMCIA), SCM SCR331-DI NTTCom, SCM Micro SCR 3310-NTTCom,
162 Cherry ST-1044U, Cherry SmartTerminal ST-2XXX
163 - add support of PC/SC v2 part 10 CM_IOCTL_GET_FEATURE_REQUEST add
164 support of FEATURE_VERIFY_PIN_DIRECT and FEATURE_MODIFY_PIN_DIRECT
165 remove support of IOCTL_SMARTCARD_VENDOR_VERIFY_PIN (now
166 obsoleted). A sample code is available in examples/scardcontrol.c
167 - we need pcsc-lite 1.2.9-beta9 since some structures used for PIN
168 pad readers are defined by pcsc-lite
169 - some (bogus) cards require an extra EGT but the ATR does not say
170 so. We try to detect the bogus cards and set TC1=2
171 - IFDHSetProtocolParameters(): only use a data rate supported by the
172 reader in the PPS negociation, otherwise we stay at the default
173 speed.
174 - calculate and store the read timeout according to the card ATR
175 instead of using a fixed value of 60 seconds
176 - increase the read timeout if the card sends and WTX request
177 - improve support of GemPC Twin and GemPC Card (serial protocol)
178 - reset the device on close only if DRIVER_OPTION_RESET_ON_CLOSE is
179 set. The problem was that a device reset also disconnects the
180 keyboard on a keyboard + reader device.
181 - use color logs
182 - some minor bugs removed
183
184
185 0.9.3 - 14 March 2005, Ludovic Rousseau
186 - change the licence from GNU GPL to GNU Lesser GPL (LGPL)
187 - add support for ACS ACR 38, Kobil KAAN Base, Kobil KAAN Advanced,
188 Kobil KAAN SIM III, Kobil KAAN mIDentity, SCM Micro SCR 331,
189 SCM Micro SCR 331-DI, SCM Micro SCR 335, SCM Micro SCR 3310,
190 SCM Micro SCR 532, Cherry XX44 readers
191 - improve communication speed with readers featuring "Automatic PPS
192 made by the CCID"
193 - switch the Cherry xx33 reader in ISO mode if power up in EMV mode
194 fails.
195 - add support of character level readers. Thanks to O2Micro for the
196 patch
197 - add support for the O2Micro OZ776S reader but the reader firmware
198 is still bogus
199 - check firmware version to avoid firmwares with bugs. You can still
200 use a bogus firmware by setting DRIVER_OPTION_USE_BOGUS_FIRMWARE
201 in Info.plist
202 - some minor bugs removed
203
204 0.9.2 - 15 August 2004, Ludovic Rousseau
205 - T=1 TPDU code:
206 . the work on T=1 TPDU code was possible thanks to Gemplus
207 validation team who helped me test, debug and bring the code to
208 an EMV validation level. Thanks to Jérôme, Jean-Yves, Xavier and
209 the Gemplus readers department
210 . error code was not checked correctly
211 . avoid a (nearly) infinite loop when resynch are needed.
212 . correctly initialise an internal value to allow more than one
213 reader to work
214 - multi-slots readers
215 . add support for multi-slots readers. The only one I have is a
216 SCM Micro SCR 331-DI with a contact and a contactless interface.
217 The contactless interface may or may not work for you since the
218 reader uses proprietary (undocumented) commands.
219 - GemPC Twin serial reader
220 . perform a command (get the reader firmware) to be sure a GemPC
221 Twin (serial or pcmcia) reader is connected
222 . use a dynamic timeout when reading the serial port.
223 The first timeout used when detecting the reader is 2 seconds to
224 not wait too long if no reader is connected. Later timeouts are
225 set to 1 minute to allow long time APDU.
226 - use `pkg-config libpcsclite --cflags` to locate the pcsc-lite
227 header files
228 - use `pkg-config --print-errors --atleast-version=1.2.9-beta5 libpcsclite`
229 to test the pcsc-lite version
230 - code improvements thanks to the splint tool (http://www.splint.org/)
231
232 0.9.1 - 1 July 2004, Ludovic Rousseau
233 - I forgot to define IFD_PARITY_ERROR in a .h file
234
235 0.9.0 - 1 July 2004, Ludovic Rousseau
236 - The T=1 TPDU automata from Carlos Prados' Towitoko driver is very
237 limited and do not support error management mechanisms.
238 I then used the T=1 TPDU automata from OpenCT (OpenSC project).
239 This automata is much more powerful but still lacks a lot of error
240 management code.
241 I then added all the needed code to reach the quality level
242 requested by the EMV standard.
243 - add support for new readers:
244 . Advanced Card Systems ACR 38
245 . Cherry XX33
246 . Dell keyboard SK-3106
247 . Dell smart card reader keyboard
248 . SCR 333
249 - add support of multi procotol cards (T=0 and T=1)
250 - the debug level is now dynamic and set in the Info.plist file (no
251 need to recompile the driver any more)
252 - add support for the libusb naming scheme: usb:%04x/%04x:libusb:%s
253 - INSTALL: add a "configuring the driver for the serial reader
254 (GemPC Twin)" part
255 - use `pkg-config libpcsclite --variable=usbdropdir` so you do not
256 have to use --enable-usbdropdir=DIR or --enable-ccidtwindir=DIR
257 even if pcscd does not use the default /usr/local/pcsc/drivers
258 - add support of IOCTL_SMARTCARD_VENDOR_IFD_EXCHANGE and
259 IOCTL_SMARTCARD_VENDOR_VERIFY_PIN in IFDHControl()
260 - read ifdDriverOptions from Info.plist to limit the use of
261 IOCTL_SMARTCARD_VENDOR_IFD_EXCHANGE (idea from Peter Williams)
262 - provide an example of use of SCardControl()
263 IOCTL_SMARTCARD_VENDOR_IFD_EXCHANGE and
264 IOCTL_SMARTCARD_VENDOR_VERIFY_PIN in example/
265 - add a --enable-pcsclite option (default to yes) so that the driver
266 can be compiled for a different framework (one needing
267 tokenparser.l like Solaris)
268 - Reset action is power off and power on, not just power on
269 - use the include files from pcsc-lite
270 - add a mechanism to allow power on at 1.8V, 3V and then 5V as
271 specified by ISO 7816. We still use 5V for now to avoid problems
272 with non ISO compliant cards
273
274 0.4.1 - 14 February 2004, Ludovic Rousseau
275 - distribute missing files readers/supported_readers.txt and
276 src/create_Info_plist.pl
277 'make install' failed because of this.
278
279 0.4.0 - 13 February 2004, Ludovic Rousseau
280 - support of T=1 with TPDU readers. A lot of the T=1 code comes from
281 Carlos Prados towitoko driver.
282 My code is GNU GPL, his code is GNU LGPL so the global driver is
283 GNU GPL
284 - PPS negotiation if the reader does not do it automatically
285 - add support for the Silitek SK-3105 keyboard. It's a USB device
286 with multiple interfaces
287 - use the create_Info_plist.pl script to generate the installed
288 Info.plist from an Info.plist template and a list of supported
289 readers. The Info.plist was too "complex" to maintain by hand
290 since it now contains 11 entries
291 - add support of IFDHCreateChannelByName to avoid wrong reader
292 enumeration. This is not complete if you have multiple _identical_
293 readers. You need to use a > 1.2.0 pcsc-lite version (not yet
294 released at that time)
295 - build but do not install the serial ccidtwin driver by default
296 since it is useless on computers without a serial port or without
297 this reader for example.
298 - read and write timeouts are not symmetric. write timout can be
299 shorter since the reader and card is not supposed to do anything
300 before receiving (write) a command
301 - do not try to find usb.h and other libusb files if
302 --disable-libusb is used. Needed if you only want to build the
303 serial driver. Thanks to Niki Waibel for the patch
304 - add a --enable-ccidtwindir argument to ./configure to specify the
305 serial GemPC Twin installation directory
306 - debug and code improvements and simplifications
307
308 0.3.2 - 4 November 2003, Ludovic Rousseau
309 - src/commands.c: correct a stupid bug that occurs with an APDU with
310 2 bytes response.
311 - Info.plist: add SPR 532 in list of supported readers
312 - parse.c: do not exit if the InterfaceClass is 0xFF (proprietary).
313 It is the case with old readers manufactured before the final
314 release of the CCID specs.
315 - move LTC31 reader from unsupported to supported reader list. It
316 was my f ault since in used odd INS byte in my test applet and odd
317 INS bytes are forbidden by ISO 7816-4 ch. 5.4.2 Instruction byte.
318 Thanks to Josep Moné s Teixidor for pointing the problem.
319 - src/commands.c: comment out the automatic GET RESPONSE part. I
320 don't think it should be in the driver. Maybe in pcscd instead?
321
322 0.3.1 - 23 September 2003, Ludovic Rouseau
323 - add --enable-multi-thread (enabled by default) for thread safe
324 support an APDU multiplexing. You will need pcsc-lite-1.2.0-rc3 or
325 above to use this feature.
326 - add --enable-libusb=PATH option is your libusb is not installed in
327 /usr or /usr/local
328 - honor DESTDIR in install rules (closes [ #300110 ]). Thanks to
329 Ville Skyttä for the patch.
330 - src/ccid.c: do not switch the GemPC Key and GemPC Twin in APDU
331 mode since it also swicth in EMV mode and may not work with non
332 EMV cards
333 - src/ccid_serial.c: complete reimplementation of the Twin serial
334 protocol using a finite state automata (code much simpler)
335
336 0.3.0 - 10 September 2003, Ludovic Rousseau
337 - support of GemPC Twin connected to a serial port. Thanks to Niki
338 W. Waibel for a working prototype.
339 - support of auto voltage at power up if the reader support it
340 instead of forcing a 5V in all cases.
341 - support of APDU mode instead of just TPDU if the reader support
342 it. Thanks to Jean-Luc Giraud for the idea and inspiration I got
343 from his "concurrent" driver.
344 - support of "time request" from the card.
345 - parse: new indentation for more readability of supported features.
346 - switch the GemPC Key and GemPC Twin in APDU mode since they
347 support it but do not announce it in the dwFeatures.
348 - new build process using autoconf/automake.
349
350 0.2.0 - 26 August 2003, Ludovic Rousseau
351 - Works under MacOS X
352 - Info.plist: use an <array></array> for the alias enumeration
353 - Makefile rework for *BSD and MacOS X
354
355 0.1.0 - 13 August 2003, Ludovic Rousseau
356 - First public release
357
358
359 Bibliography:
360 =============
361
362 [1] http://www.usb.org/developers/devclass_docs/ccid_classspec_1_00a.pdf
363 [2] http://www.gemplus.com/products/gempc433/
364 [3] http://www.gemplus.com/products/gempckey/
365 [4] http://www.gemplus.com/products/gempctwin/
366 [5] http://www.omnikey.com/en/produkt_details.php3?produkt=1&variante=47
367 [6] http://www.scmmicro.com/security/SCR331.html
368 [7] http://www.scmmicro.com/security/SCR335.html
369 [8] http://www.c3po.es/ltc31.html
370 [9] http://www.scmmicro.com/security/SPR532.html
371 [10] http://www.activcard.com/products/usb_reader.html
372 [11] http://www.scmmicro.com/security/SCR331-DI.html
373 [12] http://www.silitek.com/prod/getProduct.do?xml_id=4_2&menu_id=4_2_8&cid=1_8_5
374 [13] http://www.c3po.es/ltc32.html
375 [14] http://www.c3po.es/tltc2usb.html
376 [15] http://www.scmmicro.com/security/SCR333.html
377 [16] http://www.acs.com.hk/Product_Readers.asp?productID=107&PCate=Products_PC_Linked_SmartCard_Readers
378 [17] http://www.scmmicro.com/support/pcs_product_drivers.html
379 [18] http://www.cherrycorp.com/english/advanced-line/advanced-line_smartboard_g83-6744.htm
380 [19] http://www.kobil.com/e/products/smartcard/kaan-base.php
381 [20] http://www.kobil.com/e/products/smartcard/kaan-advanced.php
382 [21] http://www.kobil.com/d/products/smartcard/kaansim3.php
383 [22] http://www.kobil.com/e/products/index.php?s=midentity
384 [23] http://www.ntt.com/jpki/SCR331DI.html
385 [24] http://www.verisign.co.uk/products-services/security-services/unified-authentication/usb-tokens/
386 [25] http://www.eutron.com/simpocket.asp
387 [26] http://www.cryptoidentity.eutron.com/eng/home.asp
388 [27] http://www.cherry.de/english/advanced-line/advanced_smartterminal_st-1044u.htm
389 [28] http://www.ntt.com/jpki/scr3310.html
390 [29] http://www.asedrive.com/product.asp?pid=1
391 [30] http://www.scmmicro.com/security/SCR3310.html
392
393 $Id$
394
395 vim:ts=20

Properties

Name Value
svn:eol-style native
svn:keywords Author Date Id Revision

  ViewVC Help
Powered by ViewVC 1.1.5