From: Akhil Goyal <akhil.goyal@nxp.com>
To: Akash Saxena <akash.saxena@caviumnetworks.com>,
"pablo.de.lara.guarch@intel.com" <pablo.de.lara.guarch@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"Verma, Shally" <Shally.Verma@cavium.com>,
"Verma, Ayuj" <Ayuj.Verma@cavium.com>,
"Saxena, Akash" <Akash.Saxena@cavium.com>
Subject: Re: [dpdk-dev] [PATCH v2 0/2] Changes for RSA verify operation in OpenSSL PMD and unit tests
Date: Fri, 2 Nov 2018 11:44:34 +0000 [thread overview]
Message-ID: <9309eaea-3a68-d147-ee9c-a600c8f0b8e5@nxp.com> (raw)
In-Reply-To: <1540461621-28828-1-git-send-email-akash.saxena@caviumnetworks.com>
On 10/25/2018 3:30 PM, Akash Saxena wrote:
> v2:
> Added NULL check for tmp buffer allocation failure.
>
> v1:
> In lib cryptodev, RSA verify operation inputs plain message text and
> corresponding signature and expected to return
> RTE_CRYPTO_OP_STATUS_SUCCESS/FAILURE on a signature match/mismatch.
> Current OpenSSL PMD RSA verify implementation overrides application passed
> sign input by decrypted output which isn't expected.
>
> This patch addresses this issue in OpenSSL PMD. Now, OpenSSL PMD use tmp
> buffer to store sign operation decrypted output and test application to
> only check for STATUS_SUCCESS/FAILURE.
>
> ---
> Akash Saxena (2):
> crypto/openssl: changes for RSA verify operation
> test/crypto: remove data verification at rsa verify operation
>
> drivers/crypto/openssl/rte_openssl_pmd.c | 22 +++++++++++++++-------
> test/test/test_cryptodev_asym.c | 9 ++++++---
> 2 files changed, 21 insertions(+), 10 deletions(-)
>
Applied to dpdk-next-crypto
Thanks.
prev parent reply other threads:[~2018-11-02 11:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-25 10:00 Akash Saxena
2018-10-25 10:00 ` [dpdk-dev] [PATCH v2 1/2] crypto/openssl: changes for RSA verify operation Akash Saxena
2018-11-02 11:25 ` Akhil Goyal
2018-10-25 10:01 ` [dpdk-dev] [PATCH v2 2/2] test/crypto: remove data verification at rsa " Akash Saxena
2018-11-02 11:26 ` Akhil Goyal
2018-11-02 11:44 ` Akhil Goyal [this message]
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=9309eaea-3a68-d147-ee9c-a600c8f0b8e5@nxp.com \
--to=akhil.goyal@nxp.com \
--cc=Akash.Saxena@cavium.com \
--cc=Ayuj.Verma@cavium.com \
--cc=Shally.Verma@cavium.com \
--cc=akash.saxena@caviumnetworks.com \
--cc=dev@dpdk.org \
--cc=pablo.de.lara.guarch@intel.com \
/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;
as well as URLs for NNTP newsgroup(s).