DPDK patches and discussions
 help / color / mirror / Atom feed
From: Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>
To: <dev@dpdk.org>
Cc: Anoob Joseph <anoobj@marvell.com>,
	Fan Zhang <roy.fan.zhang@intel.com>,
	Brian Dooley <brian.dooley@intel.com>,
	Akhil Goyal <gakhil@marvell.com>, <jerinj@marvell.com>,
	Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>
Subject: [v1 0/2] examples/fips_validation: add ECDSA tests
Date: Tue, 27 Sep 2022 13:00:41 +0530	[thread overview]
Message-ID: <cover.1664262839.git.gmuthukrishn@marvell.com> (raw)

This series adds ECDSA validation in fips_validation app.

Depends-on: series-24851 ("FIPS asymmetric validation")

Gowrishankar Muthukrishnan (2):
  cryptodev: add enumeration in EC xform for FPM
  examples/fips_validation: add ECDSA validation

 doc/guides/sample_app_ug/fips_validation.rst  |   1 +
 examples/fips_validation/fips_validation.c    |   2 +
 examples/fips_validation/fips_validation.h    |  27 ++
 .../fips_validation/fips_validation_ecdsa.c   | 431 ++++++++++++++++++
 examples/fips_validation/main.c               | 210 ++++++++-
 examples/fips_validation/meson.build          |   1 +
 lib/cryptodev/rte_crypto_asym.h               |   3 +
 7 files changed, 672 insertions(+), 3 deletions(-)
 create mode 100644 examples/fips_validation/fips_validation_ecdsa.c

-- 
2.25.1


             reply	other threads:[~2022-09-27  7:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-27  7:30 Gowrishankar Muthukrishnan [this message]
2022-09-27  7:30 ` [v1 1/2] cryptodev: add enumeration in EC xform for FPM Gowrishankar Muthukrishnan
2022-09-28 21:35   ` Ji, Kai
2022-09-30 18:08     ` Akhil Goyal
2022-09-27  7:30 ` [v1 2/2] examples/fips_validation: add ECDSA validation Gowrishankar Muthukrishnan
2022-10-07 10:50   ` Akhil Goyal
2022-10-17  9:34   ` Dooley, Brian
2022-10-21 15:48     ` 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=cover.1664262839.git.gmuthukrishn@marvell.com \
    --to=gmuthukrishn@marvell.com \
    --cc=anoobj@marvell.com \
    --cc=brian.dooley@intel.com \
    --cc=dev@dpdk.org \
    --cc=gakhil@marvell.com \
    --cc=jerinj@marvell.com \
    --cc=roy.fan.zhang@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).