From: Stefan Berger <stefanb@linux.ibm.com>
To: yumeng <yumeng18@huawei.com>,
keyrings@vger.kernel.org, linux-crypto@vger.kernel.org,
Herbert Xu <herbert@gondor.apana.org.au>
Cc: linux-kernel@vger.kernel.org, patrick@puiterwijk.org,
linux-integrity@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>
Subject: Re: [PATCH v6 1/4] crypto: Add support for ECDSA signature verification
Date: Mon, 1 Feb 2021 08:04:27 -0500 [thread overview]
Message-ID: <f7660865-3efc-8425-d494-2e6cc9631cc5@linux.ibm.com> (raw)
In-Reply-To: <289ef2ac-d653-47b3-7771-5d8a7342ad21@huawei.com>
On 2/1/21 2:24 AM, yumeng wrote:
>
>
> 在 2021/2/1 7:32, Stefan Berger 写道:
>> +/**
>> + * ecc_get_curve() - Get a curve given its curve_id
>> + *
>> + * @curve_id: Id of the curve
>> + *
>> + * Returns pointer to the curve data, NULL if curve is not available
>> + */
>> +const struct ecc_curve *ecc_get_curve(unsigned int curve_id);
>> +
>> /**
>> * ecc_is_key_valid() - Validate a given ECDH private key
>
>
> Shall we move this definition to 'include/crypto'? Other drivers may
> also want to use it.
Maybe the driver that starts using would move it?
next prev parent reply other threads:[~2021-02-01 13:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-31 23:32 [PATCH v6 0/4] Add support for x509 certs with NIST p256 and p192 keys Stefan Berger
2021-01-31 23:32 ` [PATCH v6 1/4] crypto: Add support for ECDSA signature verification Stefan Berger
2021-02-01 7:24 ` yumeng
2021-02-01 13:04 ` Stefan Berger [this message]
2021-01-31 23:32 ` [PATCH v6 2/4] x509: Detect sm2 keys by their parameters OID Stefan Berger
2021-02-01 10:39 ` Tianjia Zhang
2021-02-01 13:02 ` Stefan Berger
2021-01-31 23:33 ` [PATCH v6 3/4] x509: Add support for parsing x509 certs with ECDSA keys Stefan Berger
2021-01-31 23:33 ` [PATCH v6 4/4] ima: Support EC keys for signature verification Stefan Berger
2021-02-01 10:36 ` Tianjia Zhang
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=f7660865-3efc-8425-d494-2e6cc9631cc5@linux.ibm.com \
--to=stefanb@linux.ibm.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=keyrings@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patrick@puiterwijk.org \
--cc=yumeng18@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;
as well as URLs for NNTP newsgroup(s).