Discussion of the VIRTIO specification
 help / color / mirror / Atom feed
From: Cornelia Huck <cohuck@redhat.com>
To: Lei He <helei.sig11@bytedance.com>,
	mst@redhat.com, virtio-comment@lists.oasis-open.org
Cc: xin.zeng@intel.com, arei.gonglei@huawei.com,
	pizhenwei@bytedance.com, helei.sig11@bytedance.com
Subject: Re: [virtio-comment] [V2 PATCH 1/1] virtio-crypto: introduce akcipher service
Date: Thu, 25 Nov 2021 18:41:42 +0100	[thread overview]
Message-ID: <87y25ci149.fsf@redhat.com> (raw)
In-Reply-To: <20211115074152.43427-2-helei.sig11@bytedance.com>

On Mon, Nov 15 2021, Lei He <helei.sig11@bytedance.com> wrote:

> Introduce akcipher (asymmetric key cipher) service type, several
> asymmetric algorithms and relevent information:
>   - RSA(padding algorithm, ASN.1 schema definition)
>   - ECDSA(ECC algorithm)
>
> Signed-off-by: zhenwei pi <pizhenwei@bytedance.com>
> Signed-off-by: Lei He <helei.sig11@bytedance.com>
> ---
>  virtio-crypto.tex | 310 +++++++++++++++++++++++++++++++++++++++++++++++++++++-
>  1 file changed, 305 insertions(+), 5 deletions(-)
>

I don't really feel qualified enough to review crypto things like this;
is anyone else well enough versed in crypto to look at the details here?


This publicly archived list offers a means to provide input to the
OASIS Virtual I/O Device (VIRTIO) TC.

In order to verify user consent to the Feedback License terms and
to minimize spam in the list archive, subscription is required
before posting.

Subscribe: virtio-comment-subscribe@lists.oasis-open.org
Unsubscribe: virtio-comment-unsubscribe@lists.oasis-open.org
List help: virtio-comment-help@lists.oasis-open.org
List archive: https://lists.oasis-open.org/archives/virtio-comment/
Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists
Committee: https://www.oasis-open.org/committees/virtio/
Join OASIS: https://www.oasis-open.org/join/


  reply	other threads:[~2021-11-25 17:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-15  7:41 [virtio-comment] [V2 PATCH 0/1] Introduce virtio asymmetric crypto service Lei He
2021-11-15  7:41 ` [virtio-comment] [V2 PATCH 1/1] virtio-crypto: introduce akcipher service Lei He
2021-11-25 17:41   ` Cornelia Huck [this message]
2021-11-30  2:53     ` zhenwei pi
2021-12-07 12:10   ` [virtio-comment] PING: " 何磊
2021-12-08 12:14     ` [virtio-comment] " Michael S. Tsirkin
2021-12-08 12:54       ` [virtio-comment] Re: [External] " 何磊
2021-11-22  3:44 ` [virtio-comment] PING: [V2 PATCH 0/1] Introduce virtio asymmetric crypto service 何磊

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=87y25ci149.fsf@redhat.com \
    --to=cohuck@redhat.com \
    --cc=arei.gonglei@huawei.com \
    --cc=helei.sig11@bytedance.com \
    --cc=mst@redhat.com \
    --cc=pizhenwei@bytedance.com \
    --cc=virtio-comment@lists.oasis-open.org \
    --cc=xin.zeng@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