DPDK patches and discussions
 help / color / mirror / Atom feed
From: Akash Saxena <akash.saxena@caviumnetworks.com>
To: pablo.de.lara.guarch@intel.com
Cc: dev@dpdk.org, akhil.goyal@nxp.com,
	shally.verma@caviumnetworks.com, ayuj.verma@caviumnetworks.com,
	Akash Saxena <akash.saxena@caviumnetworks.com>
Subject: [dpdk-dev] [PATCH v1 0/2] Changes for RSA verify operation in OpenSSL PMD and unit tests
Date: Thu, 11 Oct 2018 19:13:09 +0530	[thread overview]
Message-ID: <1539265391-9606-1-git-send-email-akash.saxena@caviumnetworks.com> (raw)

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.

Signed-off-by: Ayuj Verma <ayuj.verma@caviumnetworks.com>
Signed-off-by: Akash Saxena <akash.saxena@caviumnetworks.com>
Signed-off-by: Shally Verma <shally.verma@caviumnetworks.com>

---
Akash Saxena (2):
  crypto/openssl: changes for RSA verify operation
  test/crypto: check for operation status only at output of RSA verify
    crypto operation

 drivers/crypto/openssl/rte_openssl_pmd.c | 20 +++++++++++++-------
 test/test/test_cryptodev_asym.c          |  9 ++++++---
 2 files changed, 19 insertions(+), 10 deletions(-)

-- 
2.7.4

             reply	other threads:[~2018-10-11 13:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-11 13:43 Akash Saxena [this message]
2018-10-11 13:43 ` [dpdk-dev] [PATCH v1 1/2] crypto/openssl: changes for RSA verify operation Akash Saxena
2018-10-16 13:15   ` Akhil Goyal
2018-10-16 13:17   ` Akhil Goyal
2018-10-11 13:43 ` [dpdk-dev] [PATCH v1 2/2] test/crypto: remove data verification at rsa " Akash Saxena
2018-10-16 13:21   ` Akhil Goyal
2018-10-22 12:29     ` Verma, Shally
2018-10-24 13:09       ` Akhil Goyal

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=1539265391-9606-1-git-send-email-akash.saxena@caviumnetworks.com \
    --to=akash.saxena@caviumnetworks.com \
    --cc=akhil.goyal@nxp.com \
    --cc=ayuj.verma@caviumnetworks.com \
    --cc=dev@dpdk.org \
    --cc=pablo.de.lara.guarch@intel.com \
    --cc=shally.verma@caviumnetworks.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).