From mstjohns at comcast.net  Thu Feb  4 11:22:52 2021
From: mstjohns at comcast.net (Michael StJohns)
Date: Thu, 4 Feb 2021 11:22:52 -0500
Subject: [Pcsclite-muscle] PCSC 10 - Class 2
Message-ID: <18270375-19f2-6384-2797-3b2da0c7dc9f@comcast.net>

Hi -

I'm looking for guidance that appears to be missing from the PCSC part 
10 - specifically how ModifyPinStart/ModifyPinFinish/GetKeyPressed 
behave in the face of the normal, old pin/new pin/new pin again pattern 
for changing a pin.?? It's not directly tied to pcsc-lite, but I figured 
since Ludovic had a hand in writing the specs....

Basically, I'd like to provide a pop up visual reference of what's 
happening on the key pad - e.g. a "*" for every key pressed, a message 
when the pin and new pin are entered for a pinpad without a display.

In a class 2 device with an LCD, I can specify that the Pinpad accepts 
up to three PIN entries (with associated messages) - Old Pin, New Pin 
and Confirm New Pin using ModifyPinDirect and display those on the LCD.? 
I assume I can do that for ModifyPinStart as well on a class 2 Pinpad 
device without a display?

The question is, assuming I set bNumberMessage to 3, is what is the 
sequence of values I should see from FEATURE_GET_KEY_PRESSED and whether 
I should call FEATURE_ABORT at some point?

Let's pretend that the current pin is 1234 and that I want to change it 
to 4321 - what I think I should be seeing is something like the following:

0x2b - number key pressed - 1
0x2b - 2
0x00 - no key pressed (waiting)
0x2b - 4
0x08 - backspace - erase the 4
0x2b - 3
0x2b - 4
0x0d - OK button - old pin has been entered
0x00 - waiting
0x2b - 4
0x2b - 3
0x2b - 2
0x2b - 1
0x0d - OK Button pressed - new pin has been entered once
0x2b - 4
0x2b - 3
0x2b - 2
0x2b - 1
0x0d - OK Button pressed - new pin has been entered a second time
- at this point call FEATURE_MODIFY_PIN_FINISH

If I saw either of 0x1B or 0x40 or 0x0e I would call FEATURE_ABORT at 
that point and then return a fake RAPDU with the appropriate SW1SW2 to 
indicate the failure.

Does the above make sense or am I just going to have to find enough 
devices to try different approaches?

Thanks - Mike




From ludovic.rousseau at gmail.com  Thu Feb  4 16:23:11 2021
From: ludovic.rousseau at gmail.com (Ludovic Rousseau)
Date: Thu, 4 Feb 2021 22:23:11 +0100
Subject: [Pcsclite-muscle] PCSC 10 - Class 2
In-Reply-To: <18270375-19f2-6384-2797-3b2da0c7dc9f@comcast.net>
References: <18270375-19f2-6384-2797-3b2da0c7dc9f@comcast.net>
Message-ID: <CAGstE8ByTaYDAybdNWrEWc7obiVz1dxd50h2Hm7hOFwB+YQJxA@mail.gmail.com>

Le jeu. 4 f?vr. 2021 ? 17:24, Michael StJohns <mstjohns at comcast.net> a
?crit :> Hi -

Hello,

> I'm looking for guidance that appears to be missing from the PCSC part
> 10 - specifically how ModifyPinStart/ModifyPinFinish/GetKeyPressed
> behave in the face of the normal, old pin/new pin/new pin again pattern
> for changing a pin.   It's not directly tied to pcsc-lite, but I figured
> since Ludovic had a hand in writing the specs....

I never played with the ModifyPinStart/ModifyPinFinish/GetKeyPressed features.

I guess you are using Windows? Or at least _not_ my CCID driver. Exact?

Bye

-- 
 Dr. Ludovic Rousseau


From mstjohns at comcast.net  Thu Feb  4 17:50:49 2021
From: mstjohns at comcast.net (Michael StJohns)
Date: Thu, 4 Feb 2021 17:50:49 -0500
Subject: [Pcsclite-muscle] PCSC 10 - Class 2
In-Reply-To: <CAGstE8ByTaYDAybdNWrEWc7obiVz1dxd50h2Hm7hOFwB+YQJxA@mail.gmail.com>
References: <18270375-19f2-6384-2797-3b2da0c7dc9f@comcast.net>
 <CAGstE8ByTaYDAybdNWrEWc7obiVz1dxd50h2Hm7hOFwB+YQJxA@mail.gmail.com>
Message-ID: <f6769247-c0eb-a2cb-e3d1-d0fc40d00a06@comcast.net>

On 2/4/2021 4:23 PM, Ludovic Rousseau wrote:
> Le jeu. 4 f?vr. 2021 ? 17:24, Michael StJohns <mstjohns at comcast.net> a
> ?crit :> Hi -
>
> Hello,
>
>> I'm looking for guidance that appears to be missing from the PCSC part
>> 10 - specifically how ModifyPinStart/ModifyPinFinish/GetKeyPressed
>> behave in the face of the normal, old pin/new pin/new pin again pattern
>> for changing a pin.   It's not directly tied to pcsc-lite, but I figured
>> since Ludovic had a hand in writing the specs....
> I never played with the ModifyPinStart/ModifyPinFinish/GetKeyPressed features.
>
> I guess you are using Windows? Or at least _not_ my CCID driver. Exact?
>
> Bye
>
Hi Ludovic -

I'm actually using Java as the high level language with the desire to 
make this work over both Windows and Linuxm? so both. On the linux side 
I may or may not have been using your CCID driver for a given reader - 
to be honest I've lost track of what last worked when I was on Linux.? 
I've had mostly good luck with normal PCSC interactions on both 
platforms with with the occasional exception where a reader works in 
extended APDU mode on Windows, but not on Linux.

I've also had reasonable luck finding a generic VerifyPin/ModifyPin 
structure that works across at least a few Pinpad readers with LCDs.? 
Now I'm branching out to verify similar operating models for Pinpad 
readers without LCDs hence the question about 
ModifyPinStart/Finish/KeyPressed/Abort.

I'm guessing how thing should work - so next step is to write a test 
program and see for sure.

Thanks - Mike






From mstjohns at comcast.net  Thu Feb  4 19:50:26 2021
From: mstjohns at comcast.net (Michael StJohns)
Date: Thu, 4 Feb 2021 19:50:26 -0500
Subject: [Pcsclite-muscle] PCSC 10 - Class 2
In-Reply-To: <f6769247-c0eb-a2cb-e3d1-d0fc40d00a06@comcast.net>
References: <18270375-19f2-6384-2797-3b2da0c7dc9f@comcast.net>
 <CAGstE8ByTaYDAybdNWrEWc7obiVz1dxd50h2Hm7hOFwB+YQJxA@mail.gmail.com>
 <f6769247-c0eb-a2cb-e3d1-d0fc40d00a06@comcast.net>
Message-ID: <cd240c0f-c9ab-fddb-f3d0-635284bb95a0@comcast.net>

Hmm... I should have looked here first: 
https://ludovicrousseau.blogspot.com/2011/10/? with respect your library 
and its support for these command sequences.

Thanks - Mike


On 2/4/2021 5:50 PM, Michael StJohns wrote:
> On 2/4/2021 4:23 PM, Ludovic Rousseau wrote:
>> Le jeu. 4 f?vr. 2021 ? 17:24, Michael StJohns <mstjohns at comcast.net> a
>> ?crit :> Hi -
>>
>> Hello,
>>
>>> I'm looking for guidance that appears to be missing from the PCSC part
>>> 10 - specifically how ModifyPinStart/ModifyPinFinish/GetKeyPressed
>>> behave in the face of the normal, old pin/new pin/new pin again pattern
>>> for changing a pin.?? It's not directly tied to pcsc-lite, but I 
>>> figured
>>> since Ludovic had a hand in writing the specs....
>> I never played with the ModifyPinStart/ModifyPinFinish/GetKeyPressed 
>> features.
>>
>> I guess you are using Windows? Or at least _not_ my CCID driver. Exact?
>>
>> Bye
>>
> Hi Ludovic -
>
> I'm actually using Java as the high level language with the desire to 
> make this work over both Windows and Linuxm? so both. On the linux 
> side I may or may not have been using your CCID driver for a given 
> reader - to be honest I've lost track of what last worked when I was 
> on Linux.? I've had mostly good luck with normal PCSC interactions on 
> both platforms with with the occasional exception where a reader works 
> in extended APDU mode on Windows, but not on Linux.
>
> I've also had reasonable luck finding a generic VerifyPin/ModifyPin 
> structure that works across at least a few Pinpad readers with LCDs.? 
> Now I'm branching out to verify similar operating models for Pinpad 
> readers without LCDs hence the question about 
> ModifyPinStart/Finish/KeyPressed/Abort.
>
> I'm guessing how thing should work - so next step is to write a test 
> program and see for sure.
>
> Thanks - Mike
>
>
>
>
>
> _______________________________________________
> pcsclite-muscle mailing list
> pcsclite-muscle at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/pcsclite-muscle




From norbert at preining.info  Sun Feb  7 02:25:41 2021
From: norbert at preining.info (Norbert Preining)
Date: Sun, 7 Feb 2021 16:25:41 +0900
Subject: [Pcsclite-muscle] Fujitsu personal smart card
Message-ID: <YB+V9U7wytxfRErp@bulldog.preining.info>

Dear all,

recently I joined Fujitsu Research Labs, and here everything is
protected via a smart card that I am trying to use also from Linux.
Currently, most people use Windows (sometimes in VM) to use, but I would
prefer direct support.

The smart card is not recognized by now. 
$ opensc-tool --list-readers
# Detected readers (pcsc)
Nr.  Card  Features  Name
0    Yes             Alcor Micro AU9540 01 00

$ opensc-tool --atr
Using reader with a card: Alcor Micro AU9540 01 00
3b:f8:18:00:00:81:31:fe:45:00:73:c8:40:13:00:90:00:93

$ opensc-tool --name
Using reader with a card: Alcor Micro AU9540 01 00
Unsupported card

Is there any howto/idea/suggestions how to get started on that?

This is Debian/unstable with
ccid 1.4.34
pcscd 1.9.0 (Enabled features: Linux x86_64-pc-linux-gnu libsystemd
	serial usb libudev usbdropdir=/usr/lib/pcsc/drivers ipcdir=/run/pcscd
	filter configdir=/etc/reader.conf.d)

Thanks for any hints on how to get started.

Best

Norbert

--
PREINING Norbert                              https://www.preining.info
Fujitsu Research Labs  +  IFMGA Guide + TU Wien + TeX Live + Debian Dev
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13


From ludovic.rousseau at gmail.com  Sun Feb  7 07:45:17 2021
From: ludovic.rousseau at gmail.com (Ludovic Rousseau)
Date: Sun, 7 Feb 2021 13:45:17 +0100
Subject: [Pcsclite-muscle] Fujitsu personal smart card
In-Reply-To: <YB+V9U7wytxfRErp@bulldog.preining.info>
References: <YB+V9U7wytxfRErp@bulldog.preining.info>
Message-ID: <CAGstE8CN9KPNJzkOVJLosvm064aakAYapu7R6XdoadaXsvF=3g@mail.gmail.com>

Le dim. 7 f?vr. 2021 ? 08:27, Norbert Preining <norbert at preining.info> a ?crit :
> Dear all,

Hello Norbert,

> recently I joined Fujitsu Research Labs, and here everything is
> protected via a smart card that I am trying to use also from Linux.
> Currently, most people use Windows (sometimes in VM) to use, but I would
> prefer direct support.
>
> The smart card is not recognized by now.
> $ opensc-tool --list-readers
> # Detected readers (pcsc)
> Nr.  Card  Features  Name
> 0    Yes             Alcor Micro AU9540 01 00
>
> $ opensc-tool --atr
> Using reader with a card: Alcor Micro AU9540 01 00
>  3b:f8:18:00:00:81:31:fe:45:00:73:c8:40:13:00:90:00:93
>
> $ opensc-tool --name
> Using reader with a card: Alcor Micro AU9540 01 00
> Unsupported card
>
> Is there any howto/idea/suggestions how to get started on that?

According to the ATR the card is a "Giesecke & Devrient Sm at rtCaf? Expert 3.0"
https://smartcard-atr.apdu.fr/parse?ATR=3BF81800008131FE450073C8401300900093

I don't know if OpenSC can handle this kind of card. It will depend on
the applet loaded in the card.

You would have better answers if you ask on the OpenSC mailing list

Your second option is to find a (proprietary) PKCS#11 library for
GNU/Linux and this card.
According to https://www.usmartcards.co.uk/downloads/dl/file/id/156/product/365/starsign_crypto_usb_token.pdf
:
" Optional middleware available for Windows XP, Vista, Windows 7, Mac
OS X and Linux can handle the communication between token and host
application. "

Good luck!

Bye

-- 
 Dr. Ludovic Rousseau


From mstjohns at comcast.net  Sun Feb  7 23:25:00 2021
From: mstjohns at comcast.net (Michael StJohns)
Date: Sun, 7 Feb 2021 23:25:00 -0500
Subject: [Pcsclite-muscle] PCSC 10 - Class 2
In-Reply-To: <cd240c0f-c9ab-fddb-f3d0-635284bb95a0@comcast.net>
References: <18270375-19f2-6384-2797-3b2da0c7dc9f@comcast.net>
 <CAGstE8ByTaYDAybdNWrEWc7obiVz1dxd50h2Hm7hOFwB+YQJxA@mail.gmail.com>
 <f6769247-c0eb-a2cb-e3d1-d0fc40d00a06@comcast.net>
 <cd240c0f-c9ab-fddb-f3d0-635284bb95a0@comcast.net>
Message-ID: <e254d574-e87c-31fa-0136-552e0f76b17b@comcast.net>

Hi Ludovic -


I got a bit curious about how the VerifyPinStart/ModifyPinStart worked 
for two of the smart card readers I have - the Gemalto CT700 and the SCM 
SPR332v2.? I ended up downloading Wireshark with the USBPCap capture 
module and ran a few captures.


The answer for how they do _START_FINISH vs _DIRECT is remarkably 
similar, but different enough that it's probably not possible to do this 
in a single implementation without a lot of special casing.

The Gemalto uses the exact same sequence of USB commands for both 
_DIRECT and _START/_FINISH. Basically, the driver sends? the 
PC_TO_RDR_SECURE command (same in both cases), and the uses the URB_BULK 
command to poll the reader.?? The reader returns a CCID data block 
(after the _SECURE command and after each poll).? If the pin entry isn't 
complete, it returns one of the codes from GET_KEY_PRESSED as an error 
code (and sets the more time needed bit) if a key has been pressed, or 
blocks until the key is pressed or timed out.? If the entry is complete, 
the device returns the appropriate SW1SW2 pair and sets the error code 
to successful.??? Thinking about this model, the driver might simply 
poll on demand (GET_KEY_PRESSED) or repeatedly (_DIRECT) until the 
action completes.

The SCM does something similar to the Gemalto - but uses interrupts 
rather than polling to get the data back.??? The PC_TO_RDR_SECURE data 
structures transferred to the reader are one byte longer than is defined 
in the CCID specification (at least the 2005 version).? The extra byte I 
recorded differed by a bit between _START and _DIRECT but may actually 
not have any impact on the protocol.?? In any event, both _START and 
_DIRECT seem to use the exact same interrupt driven model to transfer 
key press information - URB_INTERRUPT - which carries 2 bytes of 
data.??? (there's an _ESCAPE command that preceeds the _SECURE call, but 
I can't find documentation on its meaning...)?? Unfortunately, the data 
provided by the interrupt does not map cleanly to? the values of 
GET_KEY_PRESSED.??? When the PC gets an interrupt indicating that the 
verify process is complete, it calls URB_BULK to retrieve the SW1SW2.? 
It looks like the driver just keeps track of what information it has 
handed to the calling process and does the right thing, either on a call 
by call basis (GET_KEY_PRESSED with _FINISH) or at the finish for _DIRECT.

I'm not sure if any of this is helpful, but thought you might find it 
interesting.

Later, Mike







On 2/4/2021 7:50 PM, Michael StJohns wrote:
> Hmm... I should have looked here first: 
> https://ludovicrousseau.blogspot.com/2011/10/? with respect your 
> library and its support for these command sequences.
>
> Thanks - Mike
>
>
> On 2/4/2021 5:50 PM, Michael StJohns wrote:
>> On 2/4/2021 4:23 PM, Ludovic Rousseau wrote:
>>> Le jeu. 4 f?vr. 2021 ? 17:24, Michael StJohns <mstjohns at comcast.net> a
>>> ?crit :> Hi -
>>>
>>> Hello,
>>>
>>>> I'm looking for guidance that appears to be missing from the PCSC part
>>>> 10 - specifically how ModifyPinStart/ModifyPinFinish/GetKeyPressed
>>>> behave in the face of the normal, old pin/new pin/new pin again 
>>>> pattern
>>>> for changing a pin.?? It's not directly tied to pcsc-lite, but I 
>>>> figured
>>>> since Ludovic had a hand in writing the specs....
>>> I never played with the ModifyPinStart/ModifyPinFinish/GetKeyPressed 
>>> features.
>>>
>>> I guess you are using Windows? Or at least _not_ my CCID driver. Exact?
>>>
>>> Bye
>>>
>> Hi Ludovic -
>>
>> I'm actually using Java as the high level language with the desire to 
>> make this work over both Windows and Linuxm? so both. On the linux 
>> side I may or may not have been using your CCID driver for a given 
>> reader - to be honest I've lost track of what last worked when I was 
>> on Linux.? I've had mostly good luck with normal PCSC interactions on 
>> both platforms with with the occasional exception where a reader 
>> works in extended APDU mode on Windows, but not on Linux.
>>
>> I've also had reasonable luck finding a generic VerifyPin/ModifyPin 
>> structure that works across at least a few Pinpad readers with LCDs.? 
>> Now I'm branching out to verify similar operating models for Pinpad 
>> readers without LCDs hence the question about 
>> ModifyPinStart/Finish/KeyPressed/Abort.
>>
>> I'm guessing how thing should work - so next step is to write a test 
>> program and see for sure.
>>
>> Thanks - Mike
>>
>>
>>
>>
>>
>> _______________________________________________
>> pcsclite-muscle mailing list
>> pcsclite-muscle at lists.infradead.org
>> http://lists.infradead.org/mailman/listinfo/pcsclite-muscle
>
>
>
> _______________________________________________
> pcsclite-muscle mailing list
> pcsclite-muscle at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/pcsclite-muscle




From norbert at preining.info  Sun Feb  7 23:32:28 2021
From: norbert at preining.info (Norbert Preining)
Date: Mon, 8 Feb 2021 13:32:28 +0900
Subject: [Pcsclite-muscle] Fujitsu personal smart card
In-Reply-To: <CAGstE8CN9KPNJzkOVJLosvm064aakAYapu7R6XdoadaXsvF=3g@mail.gmail.com>
References: <YB+V9U7wytxfRErp@bulldog.preining.info>
 <CAGstE8CN9KPNJzkOVJLosvm064aakAYapu7R6XdoadaXsvF=3g@mail.gmail.com>
Message-ID: <YCC+3JIQgbli3MTm@burischnitzel.preining.info>

Hi Ludovic,

thanks for the remarks and help, I have contacted opensc mailing list.
Doesn't sound to promising though search the web a bit :-(

All the best

Norbert

> According to the ATR the card is a "Giesecke & Devrient Sm at rtCaf? Expert 3.0"
> https://smartcard-atr.apdu.fr/parse?ATR=3BF81800008131FE450073C8401300900093

--
PREINING Norbert                              https://www.preining.info
Fujitsu Research Labs  +  IFMGA Guide + TU Wien + TeX Live + Debian Dev
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13


From ludovic.rousseau at gmail.com  Mon Feb  8 07:42:45 2021
From: ludovic.rousseau at gmail.com (Ludovic Rousseau)
Date: Mon, 8 Feb 2021 13:42:45 +0100
Subject: [Pcsclite-muscle] PCSC 10 - Class 2
In-Reply-To: <e254d574-e87c-31fa-0136-552e0f76b17b@comcast.net>
References: <18270375-19f2-6384-2797-3b2da0c7dc9f@comcast.net>
 <CAGstE8ByTaYDAybdNWrEWc7obiVz1dxd50h2Hm7hOFwB+YQJxA@mail.gmail.com>
 <f6769247-c0eb-a2cb-e3d1-d0fc40d00a06@comcast.net>
 <cd240c0f-c9ab-fddb-f3d0-635284bb95a0@comcast.net>
 <e254d574-e87c-31fa-0136-552e0f76b17b@comcast.net>
Message-ID: <CAGstE8Cpc8irzdH8KqQW5ANVzsQiojyyLHV2g0XTTCUU1Tnm8Q@mail.gmail.com>

Le lun. 8 f?vr. 2021 ? 05:26, Michael StJohns <mstjohns at comcast.net> a ?crit :
> Hi Ludovic -

Hello Michael,

> I got a bit curious about how the VerifyPinStart/ModifyPinStart worked
> for two of the smart card readers I have - the Gemalto CT700 and the SCM
> SPR332v2.  I ended up downloading Wireshark with the USBPCap capture
> module and ran a few captures.

Good idea.

> The answer for how they do _START_FINISH vs _DIRECT is remarkably
> similar, but different enough that it's probably not possible to do this
> in a single implementation without a lot of special casing.
>
> The Gemalto uses the exact same sequence of USB commands for both
> _DIRECT and _START/_FINISH. Basically, the driver sends  the
> PC_TO_RDR_SECURE command (same in both cases), and the uses the URB_BULK
> command to poll the reader.   The reader returns a CCID data block
> (after the _SECURE command and after each poll).  If the pin entry isn't
> complete, it returns one of the codes from GET_KEY_PRESSED as an error
> code (and sets the more time needed bit) if a key has been pressed, or
> blocks until the key is pressed or timed out.  If the entry is complete,
> the device returns the appropriate SW1SW2 pair and sets the error code
> to successful.    Thinking about this model, the driver might simply
> poll on demand (GET_KEY_PRESSED) or repeatedly (_DIRECT) until the
> action completes.
>
> The SCM does something similar to the Gemalto - but uses interrupts
> rather than polling to get the data back.    The PC_TO_RDR_SECURE data
> structures transferred to the reader are one byte longer than is defined
> in the CCID specification (at least the 2005 version).  The extra byte I
> recorded differed by a bit between _START and _DIRECT but may actually
> not have any impact on the protocol.   In any event, both _START and
> _DIRECT seem to use the exact same interrupt driven model to transfer
> key press information - URB_INTERRUPT - which carries 2 bytes of
> data.    (there's an _ESCAPE command that preceeds the _SECURE call, but
> I can't find documentation on its meaning...)   Unfortunately, the data
> provided by the interrupt does not map cleanly to  the values of
> GET_KEY_PRESSED.    When the PC gets an interrupt indicating that the
> verify process is complete, it calls URB_BULK to retrieve the SW1SW2.
> It looks like the driver just keeps track of what information it has
> handed to the calling process and does the right thing, either on a call
> by call basis (GET_KEY_PRESSED with _FINISH) or at the finish for _DIRECT.
>
> I'm not sure if any of this is helpful, but thought you might find it
> interesting.

It is always interesting.

The Escape command is used to send proprietary commands to the reader.
So adding support of the SCM reader in my CCID driver may be more difficult.

Do you plan to send patches for the CCID driver and pcsc-lite ? :-)

Bye

-- 
 Dr. Ludovic Rousseau


From mstjohns at comcast.net  Fri Feb 12 22:04:33 2021
From: mstjohns at comcast.net (Michael StJohns)
Date: Fri, 12 Feb 2021 22:04:33 -0500
Subject: [Pcsclite-muscle] PCSC 10 - Class 2
In-Reply-To: <CAGstE8Cpc8irzdH8KqQW5ANVzsQiojyyLHV2g0XTTCUU1Tnm8Q@mail.gmail.com>
References: <18270375-19f2-6384-2797-3b2da0c7dc9f@comcast.net>
 <CAGstE8ByTaYDAybdNWrEWc7obiVz1dxd50h2Hm7hOFwB+YQJxA@mail.gmail.com>
 <f6769247-c0eb-a2cb-e3d1-d0fc40d00a06@comcast.net>
 <cd240c0f-c9ab-fddb-f3d0-635284bb95a0@comcast.net>
 <e254d574-e87c-31fa-0136-552e0f76b17b@comcast.net>
 <CAGstE8Cpc8irzdH8KqQW5ANVzsQiojyyLHV2g0XTTCUU1Tnm8Q@mail.gmail.com>
Message-ID: <d9096c49-97a0-d7a4-d7bb-45c09f53b938@comcast.net>

On 2/8/2021 7:42 AM, Ludovic Rousseau wrote:

>> I'm not sure if any of this is helpful, but thought you might find it
>> interesting.
> It is always interesting.
>
> The Escape command is used to send proprietary commands to the reader.
> So adding support of the SCM reader in my CCID driver may be more difficult.
>
> Do you plan to send patches for the CCID driver and pcsc-lite ? :-)
>
> Bye
>
Looking harder at the SCR332 documentation suggests that the escape is 
setting the ETU so it may not be related to the _VERIFY/_MODIFY commands.

I'm trying to complete some work on Windows first, but may end up trying 
add this to your driver when I update the Linux port.? If I do, I'll 
send code.?? I've got a half dozen different Pinpad devices - I'll see 
if I can characterize them well enough to implement the various 
additional functions for each of them.


Thanks - Mike




From ludovic.rousseau at gmail.com  Tue Feb 16 11:48:09 2021
From: ludovic.rousseau at gmail.com (Ludovic Rousseau)
Date: Tue, 16 Feb 2021 17:48:09 +0100
Subject: [Pcsclite-muscle] New version of pcsc-lite: 1.9.1
Message-ID: <CAGstE8BwCf-QVdUpnfoxDmULUpuh2tFXPYiKFbOjZ6OpztMKeQ@mail.gmail.com>

Hello,

I just released a new version of pcsc-lite 1.9.1.

Changes:
1.9.1: Ludovic Rousseau
16 February 2021
- Do not (possibly) lock a reader if allocating hCard fails
- Fix a hang in SCardTransmit()
- Do not report an error if the wrong interface is used by the driver
- Update reader state when a card is removed during an exchange
- readerfactory: Make sure a freed Reader Context is not accessed
- PHSetProtocol(): supports T=0&1 cards on T=0 reader
- hotplug-libusb:
  . support CCIDCLASSDRIVER
  . add interface name to reader name
  . remove obsolete libhal scheme
- Some other minor improvements

https://ludovicrousseau.blogspot.com/2021/02/new-version-of-pcsc-lite-191.html
https://pcsclite.apdu.fr/
https://github.com/LudovicRousseau/PCSC
https://salsa.debian.org/rousseau/PCSC

-- 
 Dr. Ludovic Rousseau


