[Pcsclite-muscle] What's responsible to filter out Le in Case 4 C-APDUs under T=0?

[Francois Grieu]

On 2022-02-08 at 17:59, Ludovic Rousseau wrote :
> Can you generate a pcscd trace as documented at https://ccid.apdu.fr/#support 
> to check that?
Find it at http://mpqs.free.fr/log.txt
The trace is under mint-20.2-cinnamon-64bit with pcsc-lite version 1.8.26, using 
a GemPC USB-SL reader (which behaves as the IdBridge K30 as far as the issue 
goes under Windows with the GemPcCCID driver).
The trace shows the C-APDU as I pass it to scriptor, complete with Le. 
Everything works nicely.


> > So: is there some authoritative source on if and when ScardTransmit requires Le
> > in a C-APDU to be stripped from it's input by the caller ?
>
> I do not know any authoritative source for that question. And it may depend on 
> the reader exchange level (TPDU or APDU).
I take it as meaning this is a grey area. And I see how the application could 
test for T=0 or T=1, but not for TPDU-level vs APDU-level.

> To answer your initial question: report the problem to the Windows GemCCID 
> driver author i.e. Gemalto/Thales
Done.
     Case Number: CS1113850
     Description: GemPcCCID driver for Windows requires Le to be stripped from 
Case 4 C-APDUs**

   Francois Grieu