I would imagine that some of the cards would be sending the Request More Time byte, certainly for key generation sequences.
I suppose this would vary from Java Card to Java Card. I don't like to post benchmark results but I can say that there are quite a few speed differences in the operations across Java Card vendors ....
Best Regards,
Dave
On Mar 1, 2004, at 3:27 PM, Peter Williams wrote:
Designers of muscle-enabled ICC and readers obviously need to tune Clock speeds and timers for the 7816 UART for crypto-enabled cards - to account for the sheer amount of work being done. Operations writing to many (slow) EEPROM cells can similarly take time.<x-tad-bigger>*****************************************************************************
(a) are�people finding that T0 javacards supporting asymmetric crypto oeprations are�causing the card to regularly��issue TO procedure byte of 0x60? - i.e. request more waiting time ? .. whilst the crypto coprocessor performs the exponentiation
(b) does the javacard muscle applet's memory manager and object manager packages (that may exploit EEPROM) similarly cause requests for more wait time (when using T0)?
Peter.
Find and compare great deals on Broadband access at the MSN High-Speed Marketplace. _______________________________________________ Muscle mailing list [EMAIL PROTECTED] http://lists.musclecard.com/mailman/listinfo/muscle
David Corcoran <[EMAIL PROTECTED]>
Identity Alliance [http://www.identityalliance.com]
Smart Cards, Biometrics, Training, Identity Management
*****************************************************************************
</x-tad-bigger>
