Re: pcscd support for Class 2 SPE for Cherry SmartBoard xx44

Ludovic Rousseau <[email protected]>
Newsgroups gmane.comp.lib.muscle
Message-ID <CAGstE8AowMe-vRtFiWj+rhu5EaneYcSoofHvRLSaWz0NvcCH3Q@mail.gmail.com>
2013/8/22 Jerry Shun <[email protected]>:
> Hi,
>
> Thanks again for helping me.
> Yes, I am using the Citrix XenDesktop as the backend and app is running from the Windows VM.
> I had attached the log that was working using 1.6.4.
> I did see the same control code 0x313520 got unknown status in the log as well, but some how it did work.

This time your application is using the 2 different control codes:

First with the Windows version of CM_IOCTL_GET_FEATURE_REQUEST
winscard_svc.c:309:ContextThread() Received command: CONTROL from client 20
ifdhandler.c:1360:IFDHControl() ControlCode: 0x313520,
usb:046a/0010:libusb-1.0:5:19 (lun: 0)
Control TxBuffer:
Control RxBuffer:
ifdwrapper.c:652:IFDControl() Card not transacted: 606
ifdwrapper.c:654:IFDControl() ControlCode: 0x00313520 BytesReturned: 0
TxBuffer
RxBuffer
And it gets an error.

And then with the pcsc-lite version of CM_IOCTL_GET_FEATURE_REQUEST
ifdhandler.c:1360:IFDHControl() ControlCode: 0x42000D48,
usb:046a/0010:libusb-1.0:5:19 (lun: 0)
Control TxBuffer:
Control RxBuffer: 06 04 42 33 00 06 07 04 42 33 00 07 0A 04 42 33 00
0A 12 04 42 33 00 12
winscard_svc.c:684:ContextThread() CONTROL rv=0x0 for client 20

If your are using the SAME application with pcsc-lite 1.8.8 and 1.6.4
then that is a very strange behavior.
Are you sure it is the SAME application in both cases?

Bye

-- 
 Dr. Ludovic Rousseau
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.