On 27/03/06, Joseph Antony <[EMAIL PROTECTED]> wrote:
> On 3/27/06, Martin Paljak <[EMAIL PROTECTED]> wrote:
> > /System/Library/Frameworks/PCSC.framework/Versions/A/Headers/pcsclite.h
> >
> > It also contains a comment on the define and where to enable it
> > (everywhere) if you want to use it.
> >
> I believe that we need to update the config.h file present in
> "src/PCSC/config.h".  SmartcardServices-31 (10.4.3) seems to already
> work with large APDUs. But, I could not find any macro definition for
> PCSCLITE_ENHANCED_MESSAGING. I am confused how it works if that macro
> is not defined. What am I missing here?

You can compile your application without defining
PCSCLITE_ENHANCED_MESSAGING. It will/should work with the framework
and pcscd even if the framework and pcscd are compiled with
PCSCLITE_ENHANCED_MESSAGING.

But you can't use your application with PCSCLITE_ENHANCED_MESSAGING
defined if the framework and pcscd are not compiled with
PCSCLITE_ENHANCED_MESSAGING. You will have buffer overflows since the
framework and pcscd do not expect large APDUs.

pcsc-lite 1.3.0  #define or #undef PCSCLITE_ENHANCED_MESSAGING in
PCSC/pcsclite.h so everything should be compilted with the same
setting with this version but Apple uses a forked version based on
pcsc-lite 1.1.2.

Summary:
- you can use large APDU in your application if the framework supports it.
- you can use normal APDU in any case.
- you should not use large APDU if the framework does not support it.

The communication between the lib and pcscd should be reworked to
solve this problem (and some others). Any help or funding is welcome.

Regards,

--
  Dr. Ludovic Rousseau

_______________________________________________
Muscle mailing list
[email protected]
http://lists.drizzle.com/mailman/listinfo/muscle

Reply via email to