Hi!
I was reading the documentation for MSCComputeCrypt in
muscle-api-1.3.0.pdf, page 30, and noticed that in the example the
inData is 512 bytes long.
I understood that the MSCComputeCrypt should create the data hash, right?
I also concluded this by looking at the log of the PKCS#11 MUSCLE
Rodrigo Canellas wrote:
Hi!
I was reading the documentation for MSCComputeCrypt in
muscle-api-1.3.0.pdf, page 30, and noticed that in the example the
inData is 512 bytes long.
I understood that the MSCComputeCrypt should create the data hash, right?
I also concluded this by looking at