I changed the javacard muscle applet so that the support
for signature algorithms is now complete: its no longer necessary
to use RSA as a block cipher, merely to produce a signature. As designed,
the Javacard will sign either a TLV from the APDU, or a pre-stored object
of TLV=(ffffffffe,x, [...]x)
I noticed in passing that one cannot change a signature object, once
alloced and initialized. For example, one cannot change the algorithm,
to allow say an SHARSA signature, once the object was created to
process MD3RSA sigantures. SImialrly, one cannot change the modullus
length form that initiallly assigned. As there is no protocol facility to delete
Keypairs, this situation seems unsatisfactory.
Can anyone remember why this key initialization behavour was programmed. I can change
it so I free and realloc a persisitent KeyPair, once a change in reinitialization
parms is detected in prep for signature<-init. This would generalize the properties
of the crypto device, considerably. In the present release, linking a asymmetric
key to a specific crypto mode, and/or hashing/padding scheme, seems unecessarily
restrictive.
Find out everything you need to know about Las Vegas here for that getaway. _______________________________________________ Muscle mailing list [EMAIL PROTECTED] http://lists.musclecard.com/mailman/listinfo/muscle
