Le 09/11/2011 19:23, Frank Morgner a écrit :
> Hi!
>
>>> Ah yes, I forgot about that. It's already long ago... Anyway, the idea
>>> of sc_transmit_bytes has been given up in favor of sc_bytes2apdu, since
>>> all the opensc tools do not want to send an arbitrary buffer but an
>>> apdu.
>> Will you propose a new patch?
>>
>>>> Do you need to use SCardTransmit() or SCardControl() at the PC/SC level?
>>>> OpenSC mixes SCardTransmit() and SCardControl(). Maybe a good
>>>> evolution would be to have separate functions.
>>> PACE needs SCardControl with 0x20. Yes, I think separating control and
>>> transmit would be a good idea. In OpenSC this is currently mixed,
>>> because every buffer sent (control or not) involves APDU parsing. That's
>>> why I advocated for not parsing the buffer. But you're right that
>>> separating the functionality entirely is a cleaner approach. Is there
>>> something similar to SCardControl in OpenCT?
>> I don't think we should care much about OpenCT support of an
>> SCardControl() equivalent. OpenCT use is strongly deprecated. I do not
>> expect to see a PACE reader supporting OpenCT but not PC/SC. A void or
>> empty control() function for OpenCT would be fine with me. The idea is
>> to have the code to compile with OpenCT but in a degraded mode.
>>
>> Thanks
> If PACE is wanted (and support for nPA), I will create a patch.
>
> BTW, what is the status of SM in trunk. It used to be scheduled for
> 0.12.3. If there is clearity about how to integrate it, I could also
> provide a generic implementation of PACE (generic = "PACE done by OpenSC
> not by the reader").


There is SM dedicated github branch
https://github.com/viktorTarasov/OpenSC/tree/secure-messaging


The main development is almost finished -- still pkcs#11 has to be redesigned 
to meet the multi on-card application needs.
http://www.opensc-project.org/pipermail/opensc-devel/2011-November/017338.html


Two SM protocols are supported -- GP and CWA14890;
two types of SM usage -- 'apdu-transmit' and 'ACL'.


Development and tests where done with an external loadable SM module (commited 
the 'local' version of SM module),
there is the possibility to implement (rather invitation to improve) static 
card specific SM module.
# grep encode_apdu ./src/libopensc/*.[c,h]


GP & 'apdu-transmit' is tested with Oberthur AuthentIC 3.2,
CWA14890 & 'acl' tested with IAS/ECC card from different producers.


> Cheers, Frank.
>
>
> _______________________________________________
> opensc-devel mailing list
> opensc-devel@lists.opensc-project.org
> http://www.opensc-project.org/mailman/listinfo/opensc-devel

_______________________________________________
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel

Reply via email to