I was wrong :-) On 28/03/06, Ludovic Rousseau <[EMAIL PROTECTED]> wrote: > 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.
It will not (should not) crash or have strange effects. You will just get a SCARD_E_INSUFFICIENT_BUFFER error if you use a too big buffer. So it is safe to always use PCSCLITE_ENHANCED_MESSAGING in your application. But it will (just) not work on framework without support of PCSCLITE_ENHANCED_MESSAGING. > The communication between the lib and pcscd should be reworked to > solve this problem (and some others). Any help or funding is welcome. This remark is still valid -- Dr. Ludovic Rousseau _______________________________________________ Muscle mailing list [email protected] http://lists.drizzle.com/mailman/listinfo/muscle
