From: Hui Tang <tanghui20@huawei.com>
To: <herbert@gondor.apana.org.au>, <davem@davemloft.net>
Cc: <linux-crypto@vger.kernel.org>, <xuzaibo@huawei.com>,
<wangzhou1@hisilicon.com>, <linux-kernel@vger.kernel.org>
Subject: [PATCH v3 0/4] crypto: ecdh - register NIST P384
Date: Sat, 22 May 2021 10:44:27 +0800 [thread overview]
Message-ID: <1621651471-42010-1-git-send-email-tanghui20@huawei.com> (raw)
Register NIST P384 tfm and extend the testmgr with NIST P384 test vectors.
Summary of changes:
* crypto/ecdh.c
- fix 'ecdh_init' not unregistering NIST P192
- add ecdh_nist_p384_init_tfm
- register and unregister P384 tfm
* crypto/testmgr.c
- add test vector for P384 on vector of tests
* crypto/testmgr.h
- add test vector params for P384
---
v1 -> v2:
* Add patch#1:
- Fix ecdh-nist-p192's entry in testmgr.
- Add a comment for registering ecdh-nist-p192.
v2 - > v3:
* Fix patch#1 subject format.
---
Hui Tang (4):
crypto: ecdh - fix ecdh-nist-p192's entry in testmgr
crypto: ecdh - fix 'ecdh_init'
crypto: ecdh - register NIST P384 tfm
crypto: ecdh - add test suite for NIST P384
crypto/ecdh.c | 45 +++++++++++++++++++++++++++++++++++++++-
crypto/testmgr.c | 10 ++++++---
crypto/testmgr.h | 63 ++++++++++++++++++++++++++++++++++++++++++++++++++++++--
3 files changed, 112 insertions(+), 6 deletions(-)
--
2.8.1
next reply other threads:[~2021-05-22 2:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-22 2:44 Hui Tang [this message]
2021-05-22 2:44 ` [PATCH v3 1/4] crypto: ecdh - fix ecdh-nist-p192's entry in testmgr Hui Tang
2021-05-22 2:44 ` [PATCH v3 2/4] crypto: ecdh - fix 'ecdh_init' Hui Tang
2021-05-22 2:44 ` [PATCH v3 3/4] crypto: ecdh - register NIST P384 tfm Hui Tang
2021-05-22 2:44 ` [PATCH v3 4/4] crypto: ecdh - add test suite for NIST P384 Hui Tang
2021-05-28 7:28 ` [PATCH v3 0/4] crypto: ecdh - register " Herbert Xu
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=1621651471-42010-1-git-send-email-tanghui20@huawei.com \
--to=tanghui20@huawei.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wangzhou1@hisilicon.com \
--cc=xuzaibo@huawei.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
all inboxes | Powered by JetHome®