From: Arek Kusztal <arkadiuszx.kusztal@intel.com>
To: dev@dpdk.org
Cc: gakhil@marvell.com, roy.fan.zhang@intel.com,
Arek Kusztal <arkadiuszx.kusztal@intel.com>
Subject: [PATCH v3 1/4] crypto: add dsa random number k
Date: Fri, 11 Feb 2022 16:02:35 +0000 [thread overview]
Message-ID: <20220211160238.90065-2-arkadiuszx.kusztal@intel.com> (raw)
In-Reply-To: <20220211160238.90065-1-arkadiuszx.kusztal@intel.com>
This commit adds random number 'k' to dsa
op param struct.
This parameter is crucial in stiuations where:
- PMD cannot generate random number
- User would like to provide random source
Additionally, it makes DSA consistent with ECDSA
in terms of 'k' which includes this parameter.
Signed-off-by: Arek Kusztal <arkadiuszx.kusztal@intel.com>
---
devtools/libabigail.abignore | 5 +++++
lib/cryptodev/rte_crypto_asym.h | 4 ++++
2 files changed, 9 insertions(+)
diff --git a/devtools/libabigail.abignore b/devtools/libabigail.abignore
index 4b676f317d..4463df9dd6 100644
--- a/devtools/libabigail.abignore
+++ b/devtools/libabigail.abignore
@@ -11,3 +11,8 @@
; Ignore generated PMD information strings
[suppress_variable]
name_regexp = _pmd_info$
+
+; Ignore changes to rte_crypto_asym_op, asymmetric crypto API
+; is experimental
+[suppress_type]
+ name = rte_crypto_asym_op
\ No newline at end of file
diff --git a/lib/cryptodev/rte_crypto_asym.h b/lib/cryptodev/rte_crypto_asym.h
index 9c866f553f..e0def3d9ab 100644
--- a/lib/cryptodev/rte_crypto_asym.h
+++ b/lib/cryptodev/rte_crypto_asym.h
@@ -547,6 +547,10 @@ struct rte_crypto_dsa_op_param {
/**< Signature Generation or Verification */
rte_crypto_param message;
/**< input message to be signed or verified */
+ rte_crypto_param k;
+ /**< Per-message secret number, which is an integer
+ * in the interval (1, q-1)
+ */
rte_crypto_param r;
/**< dsa sign component 'r' value
*
--
2.13.6
next prev parent reply other threads:[~2022-02-11 17:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-11 16:02 [PATCH v3 0/4] Clarify asymmetric random, add 'k' and crypto uint Arek Kusztal
2022-02-11 16:02 ` Arek Kusztal [this message]
2022-02-11 16:02 ` [PATCH v3 2/4] crypto: clarify usage of random numbers in asym Arek Kusztal
2022-02-11 16:02 ` [PATCH v3 3/4] crypto: use rte macro instead of direct attribute Arek Kusztal
2022-02-11 16:02 ` [PATCH v3 4/4] crypto: reorganize endianness comments, add crypto uint Arek Kusztal
2022-02-12 10:52 ` [EXT] [PATCH v3 0/4] Clarify asymmetric random, add 'k' and " 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=20220211160238.90065-2-arkadiuszx.kusztal@intel.com \
--to=arkadiuszx.kusztal@intel.com \
--cc=dev@dpdk.org \
--cc=gakhil@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).