On 05/09/2016 12:24 PM, Stephan Mueller wrote: > Am Montag, 9. Mai 2016, 12:17:21 schrieb Tadeusz Struk: > > Hi Tadeusz, > >> On 05/09/2016 12:02 PM, Stephan Mueller wrote: >>> One followup: is the final memcmp() between the decrypted hash and the >>> hash of the message implemented in the RSA verify code path? At least I >>> do not see it right away. >> >> It's in line #549 > > Do you rather mean line 535? If yes, how would I provide the message digest > to > the verify function? > > Please note that at the main driver of my question is > https://git.kernel.org/cgit/linux/kernel/git/herbert/cryptodev-2.6.git/tree/crypto/asymmetric_keys/public_key.c#n143 > where the caller implements the memcmp(). >
Sorry, I misread your question. Yes, the final data comparison needs to be done by the user. We don't have the original msg (or its digest) in the context of the verify operation. The only thing we are given is the encrypted message (and the key to decrypt it). And you are right, in this case it is done in: https://git.kernel.org/cgit/linux/kernel/git/herbert/cryptodev-2.6.git/tree/crypto/asymmetric_keys/public_key.c#n143 Thanks, -- TS -- To unsubscribe from this list: send the line "unsubscribe linux-crypto" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
