On 29/03/06, Ulf Leichsenring <[EMAIL PROTECTED]> wrote: > Ludovic Rousseau wrote: > > 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. > > Is it possible to set large APDU support to be default?
Yes. You can do whatever you want. Just recompile the source code with the correct option. > I'm working with Siemens CardOS M4.3B Cards and keys/certificates with > 2048 Bit RSA keys at the moment. For this keysize the --extended-apdu > option is neccessary. > > What disadvanteges do I get, when I enable large APDUs in the framework? You will consume (a lot) more memory. with large APDU activated (at least): (1<<17)*16*16 = 32 MB without large APDU activated: 2048*16*16 = 512 KB This memory is allocated by winscard_svc.c on pcscd side. You will also consume more memory on the library side since you will use two buffers (in and out) of 128 KB instead of two buffers of 2 KB. It is just a problem of ressources (memory and CPU) consumption. The communication between the library and the daemon is not terribly efficient and should be improved. Do you want to fincancially participate is this evolution? Regards, -- Dr. Ludovic Rousseau _______________________________________________ Muscle mailing list [email protected] http://lists.drizzle.com/mailman/listinfo/muscle
