From trenta.sis at gmail.com  Mon Jan  8 04:38:31 2018
From: trenta.sis at gmail.com (Trenta sis)
Date: Mon, 8 Jan 2018 13:38:31 +0100
Subject: [Pcsclite-muscle] pcsc-lite 1.8.23
Message-ID: <CANTbh_-t7GyMeYnZAMk0XXiFGpOqVABK96bbMC=wC14Np2eDOg@mail.gmail.com>

Hi,

We are trying to compile a new versions pcsc-lite 1.8.23 and in
./configure appears a message that we have to
disable-libsystemd or uuse a source package, for now I have added
--disable-libsystemd, but I'm not sure if this is the correct option.

I 'am using this packages with thinstation and I like to know what is
the best practice in this situation.

Thanks

<div id="DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2"><br /> <table
style="border-top: 1px solid #D3D4DE;">
	<tr>
      <td style="width: 55px; padding-top: 18px;"><a
href="http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail"
target="_blank"><img
src="https://ipmcdn.avast.com/images/icons/icon-envelope-tick-green-avg-v1.png"
alt="" width="46" height="29" style="width: 46px; height: 29px;"
/></a></td>
		<td style="width: 470px; padding-top: 17px; color: #41424e;
font-size: 13px; font-family: Arial, Helvetica, sans-serif;
line-height: 18px;">Libre de virus. <a
href="http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail"
target="_blank" style="color: #4453ea;">www.avg.com</a> 		</td>
	</tr>
</table>
<a href="#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2" width="1" height="1"></a></div>


From ludovic.rousseau at free.fr  Mon Jan  8 09:24:41 2018
From: ludovic.rousseau at free.fr (Ludovic Rousseau)
Date: Mon, 8 Jan 2018 18:24:41 +0100
Subject: [Pcsclite-muscle] pcsc-lite 1.8.23
In-Reply-To: <CANTbh_-t7GyMeYnZAMk0XXiFGpOqVABK96bbMC=wC14Np2eDOg@mail.gmail.com>
References: <CANTbh_-t7GyMeYnZAMk0XXiFGpOqVABK96bbMC=wC14Np2eDOg@mail.gmail.com>
Message-ID: <51bdac2a-1c7b-4afe-b81e-5c64eccc4bf4@free.fr>

Le 08/01/2018 ? 13:38, Trenta sis a ?crit?:
> Hi,

Hello,

> We are trying to compile a new versions pcsc-lite 1.8.23 and in
> ./configure appears a message that we have to
> disable-libsystemd or uuse a source package, for now I have added
> --disable-libsystemd, but I'm not sure if this is the correct option.
> 
> I 'am using this packages with thinstation and I like to know what is
> the best practice in this situation.

If you do not use systemd then you will not benefit from pcscd autostart.
See https://ludovicrousseau.blogspot.fr/2011/11/pcscd-auto-start-using-systemd.html

If your thinstation does not have systemd then you do not (really) have a choice to use it or not.

Bye

-- 
  Dr. Ludovic Rousseau


From trenta.sis at gmail.com  Thu Jan 18 11:39:37 2018
From: trenta.sis at gmail.com (Trenta sis)
Date: Thu, 18 Jan 2018 20:39:37 +0100
Subject: [Pcsclite-muscle] smartcard
Message-ID: <CANTbh_94tCnWqyeCi5fdKACEsFgKVy0yP6mNm-JB48cW7PeBGQ@mail.gmail.com>

Hi,

I have a smartcard that we have some problems with cherry KC SC1000 (I
think that supported)

Running pcsc_scan I receive some error like atr analysis not found...

./pcsc_scan
PC/SC device scanner
V 1.5.2 (c) 2001-2017, Ludovic Rousseau <ludovic.rousseau at free.fr>
Using reader plug'n play mechanism
Scanning present readers...
0: Cherry KC 1000 SC [KC 1000 SC] 00 00

Thu Jan 18 21:22:27 2018
 Reader 0: Cherry KC 1000 SC [KC 1000 SC] 00 00
  Card state: Card inserted,
  ATR: 3B BB 18 00 C0 10 31 FE 45 80 67 04 12 B0 03 03 00 00 81 05 3C

sh: ATR_analysis: not found
ATR_analysis '3B BB 18 00 C0 10 31 FE 45 80 67 04 12 B0 03 03 00 00 81
05 3C': Success

How can I find where is the issue, smartcard, smartcard reader,...
software... I like to discard any incompatibility problem with pcsc
software.

Anybody can help?

All tests made with latest versions ccid, pcsc-lite and pcsc-tools


thanks<div id="DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2"><br /> <table
style="border-top: 1px solid #D3D4DE;">
	<tr>
      <td style="width: 55px; padding-top: 18px;"><a
href="http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail"
target="_blank"><img
src="https://ipmcdn.avast.com/images/icons/icon-envelope-tick-green-avg-v1.png"
alt="" width="46" height="29" style="width: 46px; height: 29px;"
/></a></td>
		<td style="width: 470px; padding-top: 17px; color: #41424e;
font-size: 13px; font-family: Arial, Helvetica, sans-serif;
line-height: 18px;">Libre de virus. <a
href="http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail"
target="_blank" style="color: #4453ea;">www.avg.com</a> 		</td>
	</tr>
</table>
<a href="#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2" width="1" height="1"></a></div>


From 00cpxxx at gmail.com  Thu Jan 18 12:12:04 2018
From: 00cpxxx at gmail.com (Bruno Jesus)
Date: Thu, 18 Jan 2018 18:12:04 -0200
Subject: [Pcsclite-muscle] smartcard
In-Reply-To: <CANTbh_94tCnWqyeCi5fdKACEsFgKVy0yP6mNm-JB48cW7PeBGQ@mail.gmail.com>
References: <CANTbh_94tCnWqyeCi5fdKACEsFgKVy0yP6mNm-JB48cW7PeBGQ@mail.gmail.com>
Message-ID: <CALF_nUSTV-ctoYF6Z58DjMEf-9-1vF3PVuUs0TyK7=ejtbxuCA@mail.gmail.com>

On Thu, Jan 18, 2018 at 5:39 PM, Trenta sis <trenta.sis at gmail.com> wrote:
>
> Hi,
>
> I have a smartcard that we have some problems with cherry KC SC1000 (I
> think that supported)
>
> Running pcsc_scan I receive some error like atr analysis not found...
>
> ./pcsc_scan
> PC/SC device scanner
> V 1.5.2 (c) 2001-2017, Ludovic Rousseau <ludovic.rousseau at free.fr>
> Using reader plug'n play mechanism
> Scanning present readers...
> 0: Cherry KC 1000 SC [KC 1000 SC] 00 00
>
> Thu Jan 18 21:22:27 2018
>  Reader 0: Cherry KC 1000 SC [KC 1000 SC] 00 00
>   Card state: Card inserted,
>   ATR: 3B BB 18 00 C0 10 31 FE 45 80 67 04 12 B0 03 03 00 00 81 05 3C
>
> sh: ATR_analysis: not found
> ATR_analysis '3B BB 18 00 C0 10 31 FE 45 80 67 04 12 B0 03 03 00 00 81
> 05 3C': Success
>
> How can I find where is the issue, smartcard, smartcard reader,...
> software... I like to discard any incompatibility problem with pcsc
> software.
>

I don't think there is any error in what you are seeing. The analysis
just don't know which card that ATR corresponds to. Is that the
problem you have? Or there are other problems like unresponsive card
when transmitting some APDU.

Actually that ATR is listed as a known ATR.
http://ludovic.rousseau.free.fr/softwares/pcsc-tools/smartcard_list.txt


From ludovic.rousseau at free.fr  Fri Jan 19 04:35:19 2018
From: ludovic.rousseau at free.fr (Ludovic Rousseau)
Date: Fri, 19 Jan 2018 13:35:19 +0100
Subject: [Pcsclite-muscle] smartcard
In-Reply-To: <CANTbh_94tCnWqyeCi5fdKACEsFgKVy0yP6mNm-JB48cW7PeBGQ@mail.gmail.com>
References: <CANTbh_94tCnWqyeCi5fdKACEsFgKVy0yP6mNm-JB48cW7PeBGQ@mail.gmail.com>
Message-ID: <f3248b09-bd54-2bf5-fe72-6a11f5f32f12@free.fr>

Le 18/01/2018 ? 20:39, Trenta sis a ?crit?:
> Hi,

Hello,

> I have a smartcard that we have some problems with cherry KC SC1000 (I
> think that supported)
> 
> Running pcsc_scan I receive some error like atr analysis not found...

That is exactly the problem: ATR_analysis is not found.

You need to use "make install" in the pcsc-tools directory to install the ATR_analysis command.

A far easier solution is to use a pcsc-tools package for your GNU/Linux distribution.

> 
> ./pcsc_scan
> PC/SC device scanner
> V 1.5.2 (c) 2001-2017, Ludovic Rousseau <ludovic.rousseau at free.fr>
> Using reader plug'n play mechanism
> Scanning present readers...
> 0: Cherry KC 1000 SC [KC 1000 SC] 00 00
> 
> Thu Jan 18 21:22:27 2018
>   Reader 0: Cherry KC 1000 SC [KC 1000 SC] 00 00
>    Card state: Card inserted,
>    ATR: 3B BB 18 00 C0 10 31 FE 45 80 67 04 12 B0 03 03 00 00 81 05 3C
> 
> sh: ATR_analysis: not found
> ATR_analysis '3B BB 18 00 C0 10 31 FE 45 80 67 04 12 B0 03 03 00 00 81
> 05 3C': Success
> 
> How can I find where is the issue, smartcard, smartcard reader,...
> software... I like to discard any incompatibility problem with pcsc
> software.
> 
> Anybody can help?
> 
> All tests made with latest versions ccid, pcsc-lite and pcsc-tools

I don't know what your definition of "latest" is.

To give all the needed details please follow https://pcsclite.alioth.debian.org/ccid.html#support

Regards,

-- 
  Dr. Ludovic Rousseau


From jras at dia.uned.es  Sat Jan 20 09:09:39 2018
From: jras at dia.uned.es (Jose Ramon Alvarez-Sanchez)
Date: Sat, 20 Jan 2018 17:09:39 +0000
Subject: [Pcsclite-muscle] C3PO LTC31-v2 does not have a pinpad as reported
 by CCID
Message-ID: <VI1PR0702MB3679BE6E2D0408E5B4FC2C6F90EE0@VI1PR0702MB3679.eurprd07.prod.outlook.com>

Hi,
I am using a C3PO LTC31-v2 card-reader. It does NOT have a pinpad,
but the usb ccid reports it have one, so when trying to use a card,
the software stops and waits for the inexistent pinpad to reply.

My system is Debian testing with libccid package (version 1.4.28-2)
and libpcsclite1, pcscd packages (version 1.8.23-1).
The output of ccid parse for the reader is attached to this message.
Some years ago it worked OK, but now something has changed, and the
manufacturer does not exists any more.

I have downloaded the git repository for CCID and modified it to add
an exception for the card-reader, so it can ignore the false pinpad
reported erroneously. After installing the modified ccid, it works OK.

The modification was simply to add in src/ccid.h a new line
in section "/* Product identification for special treatments */"
(under the line for LTC31):
    #define LTC31_V20x07830006
and to add in src/ccid.c a new line just before line 495 that
says "/* The chip advertises pinpad but actually doesn't have one */":
case LTC31_V2:

If you want any other information, please do not hesitate to ask.
Thanks for maintaining this essential software.
Best regards,
Jose R.

AVISO LEGAL. Este mensaje puede contener informaci?n reservada y confidencial. Si usted no es el destinatario no est? autorizado a copiar, reproducir o distribuir este mensaje ni su contenido. Si ha recibido este mensaje por error, le rogamos que lo notifique al remitente.
Le informamos de que sus datos personales, que puedan constar en este mensaje, est?n incorporados a un fichero titularidad de la UNED cuya finalidad es la de mantener el contacto con usted. En cualquier momento podr? ejercer sus derechos de acceso, rectificaci?n, cancelaci?n y oposici?n ante la UNED, Departamento de Pol?tica Jur?dica de Seguridad de la Informaci?n<http://portal.uned.es/portal/page?_pageid=93,24432769,93_24432770&_dad=portal&_schema=PORTAL>, o a trav?s de la Sede electr?nica<https://sede.uned.es/> de la Universidad.


From jras at dia.uned.es  Sat Jan 20 09:12:25 2018
From: jras at dia.uned.es (Jose Ramon Alvarez-Sanchez)
Date: Sat, 20 Jan 2018 17:12:25 +0000
Subject: [Pcsclite-muscle] C3PO LTC31-v2 does not have a pinpad as
 reported by CCID
In-Reply-To: <VI1PR0702MB3679BE6E2D0408E5B4FC2C6F90EE0@VI1PR0702MB3679.eurprd07.prod.outlook.com>
References: <VI1PR0702MB3679BE6E2D0408E5B4FC2C6F90EE0@VI1PR0702MB3679.eurprd07.prod.outlook.com>
Message-ID: <VI1PR0702MB3679866EDF27D4B0117A36B590EE0@VI1PR0702MB3679.eurprd07.prod.outlook.com>

Sorry, here is the attach with ccid parse for the reader C3PO LTC31-v2
missing in my previous message.
Jose R.

AVISO LEGAL. Este mensaje puede contener informaci?n reservada y confidencial. Si usted no es el destinatario no est? autorizado a copiar, reproducir o distribuir este mensaje ni su contenido. Si ha recibido este mensaje por error, le rogamos que lo notifique al remitente.
Le informamos de que sus datos personales, que puedan constar en este mensaje, est?n incorporados a un fichero titularidad de la UNED cuya finalidad es la de mantener el contacto con usted. En cualquier momento podr? ejercer sus derechos de acceso, rectificaci?n, cancelaci?n y oposici?n ante la UNED, Departamento de Pol?tica Jur?dica de Seguridad de la Informaci?n<http://portal.uned.es/portal/page?_pageid=93,24432769,93_24432770&_dad=portal&_schema=PORTAL>, o a trav?s de la Sede electr?nica<https://sede.uned.es/> de la Universidad.
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: LTC31v2-ccid-parse-output.txt
URL: <http://lists.infradead.org/pipermail/pcsclite-muscle/attachments/20180120/b77165a8/attachment.txt>

From ludovic.rousseau at free.fr  Sun Jan 21 04:18:20 2018
From: ludovic.rousseau at free.fr (Ludovic Rousseau)
Date: Sun, 21 Jan 2018 13:18:20 +0100
Subject: [Pcsclite-muscle] C3PO LTC31-v2 does not have a pinpad as
 reported by CCID
In-Reply-To: <VI1PR0702MB3679BE6E2D0408E5B4FC2C6F90EE0@VI1PR0702MB3679.eurprd07.prod.outlook.com>
References: <VI1PR0702MB3679BE6E2D0408E5B4FC2C6F90EE0@VI1PR0702MB3679.eurprd07.prod.outlook.com>
Message-ID: <aadd1e03-0596-ca65-27c0-2a2327955d16@free.fr>

Le 20/01/2018 ? 18:09, Jose Ramon Alvarez-Sanchez a ?crit?:
> Hi,

Hello,

> I am using a C3PO LTC31-v2 card-reader. It does NOT have a pinpad,
> but the usb ccid reports it have one, so when trying to use a card,
> the software stops and waits for the inexistent pinpad to reply.
> 
> My system is Debian testing with libccid package (version 1.4.28-2)
> and libpcsclite1, pcscd packages (version 1.8.23-1).
> The output of ccid parse for the reader is attached to this message.
> Some years ago it worked OK, but now something has changed, and the
> manufacturer does not exists any more.
> 
> I have downloaded the git repository for CCID and modified it to add
> an exception for the card-reader, so it can ignore the false pinpad
> reported erroneously. After installing the modified ccid, it works OK.
> 
> The modification was simply to add in src/ccid.h a new line
> in section "/* Product identification for special treatments */"
> (under the line for LTC31):
>      #define LTC31_V20x07830006
> and to add in src/ccid.c a new line just before line 495 that
> says "/* The chip advertises pinpad but actually doesn't have one */":
> case LTC31_V2:
> 
> If you want any other information, please do not hesitate to ask.

Thanks for the parse command result.

It looks like your firmware is *newer* (bcdDevice: 2.50 instead of 0.50) than the one in the reader listed at https://pcsclite.alioth.debian.org/ccid/supported.html#0x07830x0006

The reader listed above does NOT have the problem you report.

The diff is:
@@ -1,8 +1,8 @@
   idVendor: 0x0783
    iManufacturer: C3PO
   idProduct: 0x0006
-  iProduct: USB SMART CARD READER
- bcdDevice: 0.50 (firmware release?)
+  iProduct: USB SMARTCARD READER
+ bcdDevice: 2.50 (firmware release?)
   bLength: 9
   bDescriptorType: 4
   bInterfaceNumber: 0
@@ -13,11 +13,11 @@
   bInterfaceSubClass: 0
   bInterfaceProtocol: 0
    bulk transfer, optional interrupt-IN (CCID)
- iInterface: ?
+ Can't get iInterface string
   CCID Class Descriptor
    bLength: 0x36
    bDescriptorType: 0x21
-  bcdCCID: 1.00
+  bcdCCID: 1.01
    bMaxSlotIndex: 0x00
    bVoltageSupport: 0x01
     5.0V
@@ -27,11 +27,11 @@
    dwDefaultClock: 4.000 MHz
    dwMaximumClock: 8.000 MHz
    bNumClockSupported: 0 (will use whatever is returned)
-   IFD does not support GET CLOCK FREQUENCIES request: Success
+   IFD does not support GET CLOCK FREQUENCIES request: Resource temporarily unavailable
    dwDataRate: 9600 bps
    dwMaxDataRate: 230400 bps
    bNumDataRatesSupported: 0 (will use whatever is returned)
-   IFD does not support GET_DATA_RATES request: Success
+   IFD does not support GET_DATA_RATES request: Resource temporarily unavailable
    dwMaxIFSD: 254
    dwSynchProtocols: 0x00000007
     2-wire protocol
@@ -50,5 +50,7 @@
    bClassGetResponse: 0x00
    bClassEnvelope: 0x00
    wLcdLayout: 0x0000
-  bPINSupport: 0x00
+  bPINSupport: 0x03
+   PIN Verification supported
+   PIN Modification supported
    bMaxCCIDBusySlots: 1

I fixed the problem in https://salsa.debian.org/rousseau/CCID/commit/a27a11711a9861acea3a9b43bba56ba157c670af

> Thanks for maintaining this essential software.

You are welcome.

Thanks,

-- 
  Dr. Ludovic Rousseau


From dennis.rieks at agido.com  Mon Jan 29 07:03:13 2018
From: dennis.rieks at agido.com (Dennis Rieks)
Date: Mon, 29 Jan 2018 16:03:13 +0100
Subject: [Pcsclite-muscle] Dual Interface Reader
Message-ID: <8e9258c5-bb1d-6023-c638-23a3e7064f47@agido.com>

Hello,

we are trying to access a smartcard using a dual interface reader 
(Identiv uTrust 4501 F Dual Interface Reader). If the card is inserted 
only partly, the contactless interface will detect the card fine. But 
when the card is fully inserted into the reader, the contactless reader 
will emit a card removed event and the contact reader a card inserted event.

Card inserted partly:
eventhandler.c:421:EHStatusHandlerThread() Card inserted into Identiv 
uTrust 4701 F Dual Interface Reader [uTrust 4501 F CL Reader]

Card inserted fully:
eventhandler.c:421:EHStatusHandlerThread() Card inserted into Identiv 
uTrust 4701 F Dual Interface Reader [uTrust 4501 F Contact Reader]
eventhandler.c:356:EHStatusHandlerThread() Card Removed From Identiv 
uTrust 4701 F Dual Interface Reader [uTrust 4501 F CL Reader]

The problem is that if the card is not inserted slowly, the contactless 
reader has no change to read the nfc card.

(Because we are currently using nfc cards only, the contact reader will 
fail to power the chip: "winscard.c:339:SCardConnect() Error powering up 
card", I think this is because no contact chip is present.)

Is there any way to access the nfc chip when the card is fully inserted?

Thank you very much!
Dennis

(Another strange thing: sometimes the device will be reported with name 
4701f, at other places as 4501f)



Hardware Picture:
https://deribo.de/4701.jpg



Linux drivers:
v5.0.35 (from 2015...)
https://support.identiv.com/4701f/ <https://support.identiv.com/4701f/>



Output of --version:
/usr/sbin/pcscd --version
pcsc-lite version 1.8.23.
Copyright (C) 1999-2002 by David Corcoran <corcoran at musclecard.com 
<mailto:corcoran at musclecard.com>>.
Copyright (C) 2001-2015 by Ludovic Rousseau <ludovic.rousseau at free.fr 
<mailto:ludovic.rousseau at free.fr>>.
Copyright (C) 2003-2004 by Damien Sauveron <sauveron at labri.fr 
<mailto:sauveron at labri.fr>>.
Report bugs to <pcsclite-muscle at lists.alioth.debian.org 
<mailto:pcsclite-muscle at lists.alioth.debian.org>>.
Enabled features: Linux x86_64-pc-linux-gnu serial usb libudev 
usbdropdir=/usr/local/lib/pcsc/drivers ipcdir=/var/run/pcscd 
configdir=/usr/local/etc/reader.conf.d



Output of parse command:
 ?idVendor: 0x04E6
 ? iManufacturer: Identiv
 ?idProduct: 0x5724
 ? iProduct: Identiv uTrust 4501 F Dual Interface Reader
 ?bcdDevice: 1.04 (firmware release?)
 ?bLength: 9
 ?bDescriptorType: 4
 ?bInterfaceNumber: 0
 ?bAlternateSetting: 0
 ?bNumEndpoints: 3
 ? bulk-IN, bulk-OUT and Interrupt-IN
 ?bInterfaceClass: 0x0B [Chip Card Interface Device Class (CCID)]
 ?bInterfaceSubClass: 0
 ?bInterfaceProtocol: 0
 ? bulk transfer, optional interrupt-IN (CCID)
 ?iInterface: uTrust 4501 F Contact Reader
 ?CCID Class Descriptor
 ? bLength: 0x36
 ? bDescriptorType: 0x21
 ? bcdCCID: 1.10
 ? bMaxSlotIndex: 0x00
 ? bVoltageSupport: 0x07
 ? ?5.0V
 ? ?3.0V
 ? ?1.8V
 ? dwProtocols: 0x0000 0x0003
 ? ?T=0
 ? ?T=1
 ? dwDefaultClock: 4.800 MHz
 ? dwMaximumClock: 12.000 MHz
 ? bNumClockSupported: 0 (will use whatever is returned)
 ? ?IFD does not support GET CLOCK FREQUENCIES request: Resource 
temporarily unavailable
 ? dwDataRate: 12903 bps
 ? dwMaxDataRate: 412903 bps
 ? bNumDataRatesSupported: 0 (will use whatever is returned)
 ? ?IFD does not support GET_DATA_RATES request: Resource temporarily 
unavailable
 ? dwMaxIFSD: 254
 ? dwSynchProtocols: 0x00000000
 ? dwMechanical: 0x00000000
 ? ?No special characteristics
 ? dwFeatures: 0x000104BA
 ? ?....02 Automatic parameter configuration based on ATR data
 ? ?....08 Automatic ICC voltage selection
 ? ?....10 Automatic ICC clock frequency change according to parameters
 ? ?....20 Automatic baud rate change according to frequency and Fi, Di 
params
 ? ?....80 Automatic PPS made by the CCID
 ? ?..04.. Automatic IFSD exchange as first exchange (T=1)
 ? ?01.... TPDU level exchange
 ? dwMaxCCIDMessageLength: 271 bytes
 ? bClassGetResponse: 0xFF
 ? ?echoes the APDU class
 ? bClassEnvelope: 0xFF
 ? ?echoes the APDU class
 ? wLcdLayout: 0x0000
 ? bPINSupport: 0x00
 ? bMaxCCIDBusySlots: 1
 ?idVendor: 0x04E6
 ? iManufacturer: Identiv
 ?idProduct: 0x5724
 ? iProduct: Identiv uTrust 4501 F Dual Interface Reader
 ?bcdDevice: 1.04 (firmware release?)
 ?bLength: 9
 ?bDescriptorType: 4
 ?bInterfaceNumber: 1
 ?bAlternateSetting: 0
 ?bNumEndpoints: 3
 ? bulk-IN, bulk-OUT and Interrupt-IN
 ?bInterfaceClass: 0x0B [Chip Card Interface Device Class (CCID)]
 ?bInterfaceSubClass: 0
 ?bInterfaceProtocol: 0
 ? bulk transfer, optional interrupt-IN (CCID)
 ?iInterface: uTrust 4501 F CL Reader
 ?CCID Class Descriptor
 ? bLength: 0x36
 ? bDescriptorType: 0x21
 ? bcdCCID: 1.10
 ? bMaxSlotIndex: 0x00
 ? bVoltageSupport: 0x01
 ? ?5.0V
 ? dwProtocols: 0x0000 0x0003
 ? ?T=0
 ? ?T=1
 ? dwDefaultClock: 4.800 MHz
 ? dwMaximumClock: 12.000 MHz
 ? bNumClockSupported: 0 (will use whatever is returned)
 ? ?IFD does not support GET CLOCK FREQUENCIES request: Resource 
temporarily unavailable
 ? dwDataRate: 12903 bps
 ? dwMaxDataRate: 412903 bps
 ? bNumDataRatesSupported: 0 (will use whatever is returned)
 ? ?IFD does not support GET_DATA_RATES request: Resource temporarily 
unavailable
 ? dwMaxIFSD: 1024
 ? dwSynchProtocols: 0x00000000
 ? dwMechanical: 0x00000001
 ? ?Card accept mechanism
 ? dwFeatures: 0x000404BE
 ? ?....02 Automatic parameter configuration based on ATR data
 ? ?....04 Automatic activation of ICC on inserting
 ? ?....08 Automatic ICC voltage selection
 ? ?....10 Automatic ICC clock frequency change according to parameters
 ? ?....20 Automatic baud rate change according to frequency and Fi, Di 
params
 ? ?....80 Automatic PPS made by the CCID
 ? ?..04.. Automatic IFSD exchange as first exchange (T=1)
 ? ?04.... Short and Extended APDU level exchange
 ? dwMaxCCIDMessageLength: 1034 bytes
 ? bClassGetResponse: 0xFF
 ? ?echoes the APDU class
 ? bClassEnvelope: 0xFF
 ? ?echoes the APDU class
 ? wLcdLayout: 0x0000
 ? bPINSupport: 0x00
 ? bMaxCCIDBusySlots: 1



output of LIBCCID_ifdLogLevel=0x000F pcscd --foreground --debug --apdu 
--color:
00000000 debuglog.c:291:DebugLogSetLevel() debug level=debug
00000224 debuglog.c:312:DebugLogSetCategory() Debug options: APDU
[36m00000016 [0m [34mpcscdaemon.c:268:main() Force colored logs [0m
[36m00000282 [0m configfile.l:355:DBGetReaderList() Parsing conf file: 
/etc/reader.conf.d
[36m00000036 [0m [34mpcscdaemon.c:569:main() pcsc-lite 1.8.14 daemon 
ready. [0m
[36m00002455 [0m hotplug_libudev.c:296:get_driver() Looking for a driver 
for VID: 0x1D6B, PID: 0x0002, path: /dev/bus/usb/001/001
[36m00000055 [0m hotplug_libudev.c:296:get_driver() Looking for a driver 
for VID: 0x1D6B, PID: 0x0002, path: /dev/bus/usb/001/001
[36m00000054 [0m hotplug_libudev.c:296:get_driver() Looking for a driver 
for VID: 0x045E, PID: 0x0745, path: /dev/bus/usb/001/002
[36m00000049 [0m hotplug_libudev.c:296:get_driver() Looking for a driver 
for VID: 0x045E, PID: 0x0745, path: /dev/bus/usb/001/002
[36m00000048 [0m hotplug_libudev.c:296:get_driver() Looking for a driver 
for VID: 0x045E, PID: 0x0745, path: /dev/bus/usb/001/002
[36m00000047 [0m hotplug_libudev.c:296:get_driver() Looking for a driver 
for VID: 0x1D6B, PID: 0x0002, path: /dev/bus/usb/001/001
[36m00000050 [0m hotplug_libudev.c:296:get_driver() Looking for a driver 
for VID: 0x0BDA, PID: 0x5411, path: /dev/bus/usb/001/003
[36m00000058 [0m hotplug_libudev.c:296:get_driver() Looking for a driver 
for VID: 0x04E6, PID: 0x5724, path: /dev/bus/usb/001/005
[36m00000003 [0m [34mhotplug_libudev.c:435:HPAddDevice() Adding USB 
device: Identiv uTrust 4701 F Dual Interface Reader [0m
[36m00000035 [0m [34mreaderfactory.c:1012:RFInitializeReader() 
Attempting startup of Identiv uTrust 4701 F Dual Interface Reader 
[uTrust 4501 F Contact Reader] (55041530200900) 00 00 using 
/usr/lib64/pcsc/drivers/scmccid.bundle/Contents/Linux/libscmccid.so.5.0.35 
[0m
[36m00000164 [0m [34mreaderfactory.c:897:RFBindFunctions() Loading IFD 
Handler 3.0 [0m
Loading libscmccid 5.0.35
[36m00464453 [0m [34mreaderfactory.c:350:RFAddReader() Using the pcscd 
polling thread [0m
[36m00204434 [0m hotplug_libudev.c:296:get_driver() Looking for a driver 
for VID: 0x04E6, PID: 0x5724, path: /dev/bus/usb/001/005
[36m00000040 [0m [34mhotplug_libudev.c:435:HPAddDevice() Adding USB 
device: Identiv uTrust 4701 F Dual Interface Reader [0m
[36m00000946 [0m [34mreaderfactory.c:680:RFSetReaderName() Support 200 
simultaneous readers [0m
[36m00000044 [0m [34mreaderfactory.c:1012:RFInitializeReader() 
Attempting startup of Identiv uTrust 4701 F Dual Interface Reader 
[uTrust 4501 F CL Reader] (55041530200900) 01 00 using 
/usr/lib64/pcsc/drivers/scmccid.bundle/Contents/Linux/libscmccid.so.5.0.35 
[0m
[36m00000011 [0m [34mreaderfactory.c:811:RFLoadReader() Reusing already 
loaded driver for 
/usr/lib64/pcsc/drivers/scmccid.bundle/Contents/Linux/libscmccid.so.5.0.35 
[0m
[36m00000048 [0m [34mreaderfactory.c:897:RFBindFunctions() Loading IFD 
Handler 3.0 [0m
Loading libscmccid 5.0.35
[36m00412842 [0m [34mreaderfactory.c:350:RFAddReader() Using the pcscd 
polling thread [0m
[36m00000642 [0m hotplug_libudev.c:296:get_driver() Looking for a driver 
for VID: 0x0BDA, PID: 0x5411, path: /dev/bus/usb/001/003
[36m00000127 [0m hotplug_libudev.c:296:get_driver() Looking for a driver 
for VID: 0x03EB, PID: 0x8A6E, path: /dev/bus/usb/001/007
[36m00000107 [0m hotplug_libudev.c:296:get_driver() Looking for a driver 
for VID: 0x03EB, PID: 0x8A6E, path: /dev/bus/usb/001/007
[36m00000131 [0m hotplug_libudev.c:296:get_driver() Looking for a driver 
for VID: 0x0BDA, PID: 0x5411, path: /dev/bus/usb/001/003
[36m00000111 [0m hotplug_libudev.c:296:get_driver() Looking for a driver 
for VID: 0x04B8, PID: 0x0202, path: /dev/bus/usb/001/008
[36m00000105 [0m hotplug_libudev.c:296:get_driver() Looking for a driver 
for VID: 0x0BDA, PID: 0x5411, path: /dev/bus/usb/001/003
[36m00000100 [0m hotplug_libudev.c:296:get_driver() Looking for a driver 
for VID: 0x1D6B, PID: 0x0002, path: /dev/bus/usb/001/001
[36m00000100 [0m hotplug_libudev.c:296:get_driver() Looking for a driver 
for VID: 0x05A3, PID: 0x9422, path: /dev/bus/usb/001/004
[36m00000097 [0m hotplug_libudev.c:296:get_driver() Looking for a driver 
for VID: 0x05A3, PID: 0x9422, path: /dev/bus/usb/001/004
[36m00000107 [0m hotplug_libudev.c:296:get_driver() Looking for a driver 
for VID: 0x05A3, PID: 0x9422, path: /dev/bus/usb/001/004
[36m00000151 [0m hotplug_libudev.c:296:get_driver() Looking for a driver 
for VID: 0x05A3, PID: 0x9422, path: /dev/bus/usb/001/004
[36m00000104 [0m hotplug_libudev.c:296:get_driver() Looking for a driver 
for VID: 0x05A3, PID: 0x9422, path: /dev/bus/usb/001/004
[36m00000116 [0m hotplug_libudev.c:296:get_driver() Looking for a driver 
for VID: 0x1D6B, PID: 0x0002, path: /dev/bus/usb/001/001
[36m00000134 [0m hotplug_libudev.c:296:get_driver() Looking for a driver 
for VID: 0x8087, PID: 0x0A2B, path: /dev/bus/usb/001/006
[36m00000099 [0m hotplug_libudev.c:296:get_driver() Looking for a driver 
for VID: 0x8087, PID: 0x0A2B, path: /dev/bus/usb/001/006
[36m00000149 [0m hotplug_libudev.c:296:get_driver() Looking for a driver 
for VID: 0x1D6B, PID: 0x0003, path: /dev/bus/usb/002/001
[36m00000096 [0m hotplug_libudev.c:296:get_driver() Looking for a driver 
for VID: 0x1D6B, PID: 0x0003, path: /dev/bus/usb/002/001
[36m00000099 [0m hotplug_libudev.c:296:get_driver() Looking for a driver 
for VID: 0x8564, PID: 0x1000, path: /dev/bus/usb/002/002
[36m00000095 [0m hotplug_libudev.c:296:get_driver() Looking for a driver 
for VID: 0x1D6B, PID: 0x0003, path: /dev/bus/usb/002/001
[36m00000099 [0m hotplug_libudev.c:296:get_driver() Looking for a driver 
for VID: 0x0BDA, PID: 0x0411, path: /dev/bus/usb/002/003
[36m02893410 [0m eventhandler.c:405:EHStatusHandlerThread() powerState: 
POWER_STATE_POWERED
[36m00000041 [0m [34meventhandler.c:422:EHStatusHandlerThread() Card 
inserted into Identiv uTrust 4701 F Dual Interface Reader [uTrust 4501 F 
CL Reader] (55041530200900) 01 00 [0m
[36m00000023 [0m [34mCard ATR: 3B 8F 80 01 80 4F 0C A0 00 00 03 06 03 00 
01 00 00 00 00 6A [0m
[36m04107036 [0m eventhandler.c:411:EHStatusHandlerThread() powerState: 
POWER_STATE_UNPOWERED
[36m00000044 [0m [34meventhandler.c:422:EHStatusHandlerThread() Card 
inserted into Identiv uTrust 4701 F Dual Interface Reader [uTrust 4501 F 
Contact Reader] (55041530200900) 00 00 [0m
[36m00000012 [0m [35meventhandler.c:438:EHStatusHandlerThread() Error 
powering up card. [0m
[36m00037451 [0m [34meventhandler.c:357:EHStatusHandlerThread() Card 
Removed From Identiv uTrust 4701 F Dual Interface Reader [uTrust 4501 F 
CL Reader] (55041530200900) 01 00 [0m
[36m00362893 [0m [34meventhandler.c:357:EHStatusHandlerThread() Card 
Removed From Identiv uTrust 4701 F Dual Interface Reader [uTrust 4501 F 
Contact Reader] (55041530200900) 00 00 [0m
[36m00514484 [0m eventhandler.c:411:EHStatusHandlerThread() powerState: 
POWER_STATE_UNPOWERED
[36m00000038 [0m [34meventhandler.c:422:EHStatusHandlerThread() Card 
inserted into Identiv uTrust 4701 F Dual Interface Reader [uTrust 4501 F 
Contact Reader] (55041530200900) 00 00 [0m
[36m00000012 [0m [35meventhandler.c:438:EHStatusHandlerThread() Error 
powering up card. [0m
[36m00400354 [0m [34meventhandler.c:357:EHStatusHandlerThread() Card 
Removed From Identiv uTrust 4701 F Dual Interface Reader [uTrust 4501 F 
Contact Reader] (55041530200900) 00 00 [0m
[36m00514653 [0m eventhandler.c:411:EHStatusHandlerThread() powerState: 
POWER_STATE_UNPOWERED
[36m00000034 [0m [34meventhandler.c:422:EHStatusHandlerThread() Card 
inserted into Identiv uTrust 4701 F Dual Interface Reader [uTrust 4501 F 
Contact Reader] (55041530200900) 00 00 [0m
[36m00000010 [0m [35meventhandler.c:438:EHStatusHandlerThread() Error 
powering up card. [0m
[36m05611295 [0m [34meventhandler.c:357:EHStatusHandlerThread() Card 
Removed From Identiv uTrust 4701 F Dual Interface Reader [uTrust 4501 F 
Contact Reader] (55041530200900) 00 00 [0m
[36m00019779 [0m eventhandler.c:405:EHStatusHandlerThread() powerState: 
POWER_STATE_POWERED
[36m00000036 [0m [34meventhandler.c:422:EHStatusHandlerThread() Card 
inserted into Identiv uTrust 4701 F Dual Interface Reader [uTrust 4501 F 
CL Reader] (55041530200900) 01 00 [0m
[36m00000022 [0m [34mCard ATR: 3B 8F 80 01 80 4F 0C A0 00 00 03 06 03 00 
01 00 00 00 00 6A [0m
[36m00565154 [0m [34meventhandler.c:357:EHStatusHandlerThread() Card 
Removed From Identiv uTrust 4701 F Dual Interface Reader [uTrust 4501 F 
CL Reader] (55041530200900) 01 00 [0m


From ludovic.rousseau at free.fr  Mon Jan 29 08:55:15 2018
From: ludovic.rousseau at free.fr (Ludovic Rousseau)
Date: Mon, 29 Jan 2018 17:55:15 +0100
Subject: [Pcsclite-muscle] Dual Interface Reader
In-Reply-To: <8e9258c5-bb1d-6023-c638-23a3e7064f47@agido.com>
References: <8e9258c5-bb1d-6023-c638-23a3e7064f47@agido.com>
Message-ID: <bd86c527-d2fc-8978-a97b-a11202f8442c@free.fr>

Le 29/01/2018 ? 16:03, Dennis Rieks a ?crit?:
> Hello,

Hello,

> we are trying to access a smartcard using a dual interface reader 
> (Identiv uTrust 4501 F Dual Interface Reader). If the card is inserted 
> only partly, the contactless interface will detect the card fine. But 
> when the card is fully inserted into the reader, the contactless reader 
> will emit a card removed event and the contact reader a card inserted 
> event.
> 
> Card inserted partly:
> eventhandler.c:421:EHStatusHandlerThread() Card inserted into Identiv 
> uTrust 4701 F Dual Interface Reader [uTrust 4501 F CL Reader]
> 
> Card inserted fully:
> eventhandler.c:421:EHStatusHandlerThread() Card inserted into Identiv 
> uTrust 4701 F Dual Interface Reader [uTrust 4501 F Contact Reader]
> eventhandler.c:356:EHStatusHandlerThread() Card Removed From Identiv 
> uTrust 4701 F Dual Interface Reader [uTrust 4501 F CL Reader]
> 
> The problem is that if the card is not inserted slowly, the contactless 
> reader has no change to read the nfc card.
> 
> (Because we are currently using nfc cards only, the contact reader will 
> fail to power the chip: "winscard.c:339:SCardConnect() Error powering up 
> card", I think this is because no contact chip is present.)
> 
> Is there any way to access the nfc chip when the card is fully inserted?

Maybe you can just put the card _on_ the reader instead of _inside_ the 
reader.

Bye

-- 
Dr. Ludovic Rousseau


From dennis.rieks at agido.com  Mon Jan 29 09:51:23 2018
From: dennis.rieks at agido.com (Dennis Rieks)
Date: Mon, 29 Jan 2018 18:51:23 +0100
Subject: [Pcsclite-muscle] Dual Interface Reader
In-Reply-To: <bd86c527-d2fc-8978-a97b-a11202f8442c@free.fr>
References: <8e9258c5-bb1d-6023-c638-23a3e7064f47@agido.com>
 <bd86c527-d2fc-8978-a97b-a11202f8442c@free.fr>
Message-ID: <2c503a59-02c5-d89a-19fc-a41c423f0273@agido.com>

Hello,


On 29.01.2018 17:55, Ludovic Rousseau wrote:
> Le 29/01/2018 ? 16:03, Dennis Rieks a ?crit?:
>> Hello,
>
> Hello,
>
>> we are trying to access a smartcard using a dual interface reader 
>> (Identiv uTrust 4501 F Dual Interface Reader). If the card is 
>> inserted only partly, the contactless interface will detect the card 
>> fine. But when the card is fully inserted into the reader, the 
>> contactless reader will emit a card removed event and the contact 
>> reader a card inserted event.
>>
>> Card inserted partly:
>> eventhandler.c:421:EHStatusHandlerThread() Card inserted into Identiv 
>> uTrust 4701 F Dual Interface Reader [uTrust 4501 F CL Reader]
>>
>> Card inserted fully:
>> eventhandler.c:421:EHStatusHandlerThread() Card inserted into Identiv 
>> uTrust 4701 F Dual Interface Reader [uTrust 4501 F Contact Reader]
>> eventhandler.c:356:EHStatusHandlerThread() Card Removed From Identiv 
>> uTrust 4701 F Dual Interface Reader [uTrust 4501 F CL Reader]
>>
>> The problem is that if the card is not inserted slowly, the 
>> contactless reader has no change to read the nfc card.
>>
>> (Because we are currently using nfc cards only, the contact reader 
>> will fail to power the chip: "winscard.c:339:SCardConnect() Error 
>> powering up card", I think this is because no contact chip is present.)
>>
>> Is there any way to access the nfc chip when the card is fully inserted?
>
> Maybe you can just put the card _on_ the reader instead of _inside_ 
> the reader.
Thank you for the note, but unfortunately this is not possible because 
it is the embedded version of the reader. there is only one card slot 
like the one in a cash machine. The case is made of metal and the nfc 
card is only detected when (slowly) put into the reader slot...

The Reader Slot: https://deribo.de/slot.jpg
The Reader itself: https://deribo.de/4701jpg

Does pcslite generally support two active cards (nfc and chip) in a dual 
reader at the same time? Or is the hardware telling that the nfc card 
was removed?

thank you very much
Dennis

> Bye
>



From mstjohns at comcast.net  Mon Jan 29 10:23:05 2018
From: mstjohns at comcast.net (Michael StJohns)
Date: Mon, 29 Jan 2018 13:23:05 -0500
Subject: [Pcsclite-muscle] Dual Interface Reader
In-Reply-To: <2c503a59-02c5-d89a-19fc-a41c423f0273@agido.com>
References: <8e9258c5-bb1d-6023-c638-23a3e7064f47@agido.com>
 <bd86c527-d2fc-8978-a97b-a11202f8442c@free.fr>
 <2c503a59-02c5-d89a-19fc-a41c423f0273@agido.com>
Message-ID: <7d5da4a9-198d-1c94-c788-926b98dc25cd@comcast.net>

On 1/29/2018 12:51 PM, Dennis Rieks wrote:
> Hello,
>
>
> On 29.01.2018 17:55, Ludovic Rousseau wrote:
>> Le 29/01/2018 ? 16:03, Dennis Rieks a ?crit?:
>>> Hello,
>>
>> Hello,
>>
>>> we are trying to access a smartcard using a dual interface reader 
>>> (Identiv uTrust 4501 F Dual Interface Reader). If the card is 
>>> inserted only partly, the contactless interface will detect the card 
>>> fine. But when the card is fully inserted into the reader, the 
>>> contactless reader will emit a card removed event and the contact 
>>> reader a card inserted event.
>>>
>>> Card inserted partly:
>>> eventhandler.c:421:EHStatusHandlerThread() Card inserted into 
>>> Identiv uTrust 4701 F Dual Interface Reader [uTrust 4501 F CL Reader]
>>>
>>> Card inserted fully:
>>> eventhandler.c:421:EHStatusHandlerThread() Card inserted into 
>>> Identiv uTrust 4701 F Dual Interface Reader [uTrust 4501 F Contact 
>>> Reader]
>>> eventhandler.c:356:EHStatusHandlerThread() Card Removed From Identiv 
>>> uTrust 4701 F Dual Interface Reader [uTrust 4501 F CL Reader]
>>>
>>> The problem is that if the card is not inserted slowly, the 
>>> contactless reader has no change to read the nfc card.
>>>
>>> (Because we are currently using nfc cards only, the contact reader 
>>> will fail to power the chip: "winscard.c:339:SCardConnect() Error 
>>> powering up card", I think this is because no contact chip is present.)
>>>
>>> Is there any way to access the nfc chip when the card is fully 
>>> inserted?
>>
>> Maybe you can just put the card _on_ the reader instead of _inside_ 
>> the reader.
> Thank you for the note, but unfortunately this is not possible because 
> it is the embedded version of the reader. there is only one card slot 
> like the one in a cash machine. The case is made of metal and the nfc 
> card is only detected when (slowly) put into the reader slot...
>
> The Reader Slot: https://deribo.de/slot.jpg
> The Reader itself: https://deribo.de/4701jpg
>
> Does pcslite generally support two active cards (nfc and chip) in a 
> dual reader at the same time? Or is the hardware telling that the nfc 
> card was removed?

The contact reader has a leaf switch which detects card insertion and 
triggers the contact reader (incidentally disabling the contactless 
reader).?? If you never have a need for the contact reader, you could 
probably snip the trace to the switch.? A better idea would be to 
re-mount the reader so that the antenna on the board (the back side of 
the board towards the same edge as the contact reader opening)? is 
against the outside of the case (and the case is plastic).

It's also possible that the board itself has a jumper that can be 
removed to disable the contact reader detection.

Last possibility is that the board supports an external antenna that can 
be mounted separately from the reader itself.

Good luck - Mike



>
> thank you very much
> Dennis
>
>> Bye
>>
>
>
> _______________________________________________
> pcsclite-muscle mailing list
> pcsclite-muscle at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/pcsclite-muscle




From dennis.rieks at agido.com  Tue Jan 30 04:26:11 2018
From: dennis.rieks at agido.com (Dennis Rieks)
Date: Tue, 30 Jan 2018 13:26:11 +0100
Subject: [Pcsclite-muscle] Dual Interface Reader
In-Reply-To: <8e9258c5-bb1d-6023-c638-23a3e7064f47@agido.com>
References: <8e9258c5-bb1d-6023-c638-23a3e7064f47@agido.com>
Message-ID: <f8d92fc5-f272-9e46-7b31-aac29ac3d0a5@agido.com>

Hello,

it is possible to disable the contactless switch off using SCardControl 
with escape command 0x9C 0x01. The setting is active as long as the 
reader is turned on.

Greetings
Dennis

#include <stdio.h>
#include <stdlib.h>
#include <string.h>
#include <winscard.h>
#include <reader.h>

#define IOCTL_CCID_ESCAPE SCARD_CTL_CODE(0xDAC)
unsigned const char CNTLESS_SWITCH_RF_ON_OFF[] = {0x9C, 0x01};

#define PCSC_ERROR_EXIT(rv, text) \
if (rv != SCARD_S_SUCCESS) { \
 ? ? printf(text ": %s (0x%lX)\n", pcsc_stringify_error(rv), rv); \
 ? ? return 1; \
}

int main(int argc, char *argv[]) {
 ? ? LONG rv;
 ? ? SCARDCONTEXT hContext;
 ? ? DWORD dwReaders;
 ? ? LPSTR mszReaders = NULL;
 ? ? char *ptr;
 ? ? SCARDHANDLE hCard;
 ? ? DWORD dwActiveProtocol;

 ? ? rv = SCardEstablishContext(SCARD_SCOPE_SYSTEM, NULL, NULL, &hContext);
 ? ? PCSC_ERROR_EXIT(rv, "SCardEstablishContext");
 ? ? rv = SCardListReaders(hContext, NULL, NULL, &dwReaders);
 ? ? PCSC_ERROR_EXIT(rv, "SCardListReaders")
 ? ? mszReaders = malloc(sizeof(char) * dwReaders);
 ? ? if (mszReaders == NULL) {
 ? ? ? ? printf("malloc: not enough memory\n");
 ? ? ? ? return 1;
 ? ? }
 ? ? rv = SCardListReaders(hContext, NULL, mszReaders, &dwReaders);
 ? ? PCSC_ERROR_EXIT(rv, "SCardListReaders")
 ? ? ptr = mszReaders;
 ? ? while (*ptr != '\0') {
 ? ? ? ? rv = SCardConnect(hContext, ptr, SCARD_SHARE_DIRECT,
 ? ? ? ? ? ? ? ? ? ? ? ? ? SCARD_PROTOCOL_UNDEFINED, &hCard, 
&dwActiveProtocol);
 ? ? ? ? PCSC_ERROR_EXIT(rv, "SCardConnect")
 ? ? ? ? rv = SCardControl(hCard, IOCTL_CCID_ESCAPE, 
CNTLESS_SWITCH_RF_ON_OFF, sizeof(CNTLESS_SWITCH_RF_ON_OFF),
 ? ? ? ? ? ? ? ? ? ? ? ? ? NULL, 0, NULL);
 ? ? ? ? if (rv == SCARD_S_SUCCESS) {
 ? ? ? ? ? ? printf("successfully set CNTLESS_SWITCH_RF_ON_OFF for 
reader '%s'\n", ptr);
 ? ? ? ? ? ? return 0;
 ? ? ? ? }
 ? ? ? ? ptr += strlen(ptr) + 1;
 ? ? }
 ? ? printf("No reader found\n");
 ? ? return 1;
}


-- 
Dennis Rieks

agido GmbH
Hafenpromenade 3a
44263 Dortmund

Fon: +49-231-399802-70
Fax: +49-231-399802-69
Skype: dennisrieks

http://www.agido.com/
http://www.facebook.com/agido

Amtsgericht Dortmund: HRB 20179
USt-IdNr.: DE287205768
Gesch?ftsf?hrer: Thomas Louis