From: Tadeusz Struk <tadeusz.struk@intel.com>
To: Stephan Mueller <smueller@chronox.de>
Cc: linux-crypto@vger.kernel.org
Subject: Re: pkcs1pad_verify_complete: decoding missing?
Date: Mon, 9 May 2016 12:17:21 -0700 [thread overview]
Message-ID: <ee26539d-0447-d9cc-a2d7-370cfe05781a@intel.com> (raw)
In-Reply-To: <10395258.qUa3tSVhS8@tauon.atsec.com>
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
--
TS
next prev parent reply other threads:[~2016-05-09 19:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-09 10:24 pkcs1pad_verify_complete: decoding missing? Stephan Mueller
2016-05-09 18:15 ` Tadeusz Struk
2016-05-09 18:50 ` Stephan Mueller
2016-05-09 18:55 ` Tadeusz Struk
2016-05-09 19:02 ` Stephan Mueller
2016-05-09 19:17 ` Tadeusz Struk [this message]
2016-05-09 19:24 ` Stephan Mueller
2016-05-09 19:31 ` Tadeusz Struk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ee26539d-0447-d9cc-a2d7-370cfe05781a@intel.com \
--to=tadeusz.struk@intel.com \
--cc=linux-crypto@vger.kernel.org \
--cc=smueller@chronox.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox