On Thursday 02 August 2007 20:01:13 [EMAIL PROTECTED] wrote: > I'm trying to make my kernel working with the phoenix driver from openct > but without much success for the moment. > This driver is really working ? ( I'm talking about the openct phoenix > driver ? ) Because it is very strange: > for example, the driver don't wait 500 ms after a reset. After the reset, > the driver read only one byte ( due to a very short timeout I suppose )
I was told it works with some hardware. but improvements are always welcome. > I continue my investigations... Other question: what is the maximum length > payload used by opensc for crypto function and sended to the device. > Currently I support only 252 bytes len for each INS but if it is necessary > I can create a ring buffer to have a potential buffer of 512 bytes. Is it > enough ? opensc can be configured with max_send_size and max_recv_size to the limit of the reader. either card+reader should speak t=1 and thus allow big commands in several chunks, or the card should have commands to do e.g. sending data to be signed and encrypted in chunks (and receive it as well). for some combinations this is not true, so you can't e.g. decrypt 256 bytes or raw sign 256 bytes with some cards and some readers with too small limits. so it would be good to support the highest limit the hardware can do. if apdu's with 256 bytes of data work, that is always best. Regards, Andreas _______________________________________________ opensc-devel mailing list [email protected] http://www.opensc-project.org/mailman/listinfo/opensc-devel
