a. computeCrypt( startup ) // initialize the cipher block of the hardware: supply only null-length data
b. computeCrypt( datablocks ) // to compress/hash n blocks of the datastream, storing state within the cipher block of the hardware
c. computeCrypt( finalize ) // to finalize the work of the cipher block of the hardware - and return a signature to the user. Supply a null length data.
The same pattern applies to verification of signed checksums. Watch (c) however, for verification case: it assumes 2 IN parameters, the first of which would be null-length, in this pattern.
There are some more efficient ways of using the API that suit special cases; but get the above working, first.
----- Original Message ----- From: Matteo Ferrara
To: MuscleCard Mailing List
Sent: Tuesday, November 09, 2004 12:57 AM
Subject: [Muscle] Some questions about ComputeCrypt
Good Morning,
I have some questions about ComputeCrypt function.
1)
If I use this function with MSC_DIR_SIGN direction the first step is to digesting the pInputData and after create the signature of the digest?
Alternatively the function signing directly the pInputData?
2)
If I use ComputeCrypt function with MSC_DIR_VERIFY I need to have the data and the signature but the function has only a input parameter.
How do I do to pass 2 input parameter?
Excuse me for my bad english.
Thank you very much.
Matteo Ferrara
http://digilander.libero.it/ferraram/
_______________________________________________
Muscle mailing list
[EMAIL PROTECTED]
http://lists.drizzle.com/mailman/listinfo/muscle _______________________________________________
Muscle mailing list
[EMAIL PROTECTED]
http://lists.drizzle.com/mailman/listinfo/muscle
