From: Sandy Harris <sandyinchina@gmail.com>
To: Lei He <helei.sig11@bytedance.com>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
David Howells <dhowells@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Linux Crypto Mailing List <linux-crypto@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
berrange@redhat.com, pizhenwei@bytedance.com
Subject: Re: [PATCH v2 0/4] virtio-crypto: support ECDSA algorithm
Date: Fri, 1 Jul 2022 07:12:41 +0800 [thread overview]
Message-ID: <CACXcFmmxDVBrnp3_0UzN+VbAjDaUSNtoUBz5fM1Y4u5yqL89qA@mail.gmail.com> (raw)
In-Reply-To: <CC761178-556D-44F6-9479-5151C69476C8@bytedance.com>
On Thu, Jun 30, 2022 at 4:37 PM Lei He <helei.sig11@bytedance.com> wrote:
> I have explained above why we need a driver that supports ECDSA, ...
I do not think we do. There are some security concerns.
https://en.wikipedia.org/wiki/Elliptic_Curve_Digital_Signature_Algorithm#Security
next prev parent reply other threads:[~2022-06-30 23:13 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-23 7:05 [PATCH v2 0/4] virtio-crypto: support ECDSA algorithm Lei He
2022-06-23 7:05 ` [PATCH v2 1/4] crypto: fix the calculation of max_size for ECDSA Lei He
2022-06-23 7:05 ` [PATCH v2 2/4] crypto: pkcs8 parser support ECDSA private keys Lei He
2022-06-23 7:05 ` [PATCH v2 3/4] crypto: remove unused field in pkcs8_parse_context Lei He
2022-06-23 7:05 ` [PATCH v2 4/4] virtio-crypto: support ECDSA algorithm Lei He
2022-06-24 6:51 ` [PATCH v2 0/4] " Michael S. Tsirkin
2022-06-30 6:59 ` Herbert Xu
2022-06-30 7:23 ` [External] " Lei He
2022-06-30 7:41 ` Herbert Xu
2022-06-30 8:30 ` Lei He
2022-06-30 9:07 ` Herbert Xu
2022-06-30 12:44 ` Lei He
2022-06-30 12:50 ` Lei He
2022-06-30 23:12 ` Sandy Harris [this message]
2022-07-01 2:54 ` [External] " Lei He
2022-06-30 9:48 ` [External] " Daniel P. Berrangé
2022-06-30 12:43 ` Lei He
2022-08-09 18:36 ` Michael S. Tsirkin
-- strict thread matches above, loose matches on Subject: below --
2022-06-23 6:09 Lei He
2022-06-23 6:09 ` Lei He
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=CACXcFmmxDVBrnp3_0UzN+VbAjDaUSNtoUBz5fM1Y4u5yqL89qA@mail.gmail.com \
--to=sandyinchina@gmail.com \
--cc=berrange@redhat.com \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=helei.sig11@bytedance.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=pizhenwei@bytedance.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.