From: "Michael S. Tsirkin" <mst@redhat.com>
To: "Gonglei (Arei)" <arei.gonglei@huawei.com>
Cc: 何磊 <helei.sig11@bytedance.com>,
"virtio-comment@lists.oasis-open.org"
<virtio-comment@lists.oasis-open.org>,
"pizhenwei@bytedance.com" <pizhenwei@bytedance.com>,
"xin.zeng@intel.com" <xin.zeng@intel.com>
Subject: [virtio-comment] Re: [V3 PATCH 1/1] virtio-crypto: introduce akcipher service
Date: Thu, 20 Jan 2022 05:47:08 -0500 [thread overview]
Message-ID: <20220120054600-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <46e69803beeb4741a33c89e2351370ab@huawei.com>
On Thu, Jan 20, 2022 at 08:12:49AM +0000, Gonglei (Arei) wrote:
>
>
> > -----Original Message-----
> > From: Michael S. Tsirkin [mailto:mst@redhat.com]
> > Sent: Thursday, January 20, 2022 3:27 PM
> > To: Gonglei (Arei) <arei.gonglei@huawei.com>
> > Cc: 何磊 <helei.sig11@bytedance.com>; virtio-comment@lists.oasis-open.org;
> > pizhenwei@bytedance.com; xin.zeng@intel.com
> > Subject: Re: [V3 PATCH 1/1] virtio-crypto: introduce akcipher service
> >
> > On Thu, Jan 20, 2022 at 05:48:09AM +0000, Gonglei (Arei) wrote:
> > >
> > >
> > > > -----Original Message-----
> > > > From: Michael S. Tsirkin [mailto:mst@redhat.com]
> > > > Sent: Wednesday, January 19, 2022 11:17 PM
> > > > To: 何磊 <helei.sig11@bytedance.com>
> > > > Cc: virtio-comment@lists.oasis-open.org; pizhenwei@bytedance.com;
> > > > xin.zeng@intel.com; Gonglei (Arei) <arei.gonglei@huawei.com>
> > > > Subject: Re: [V3 PATCH 1/1] virtio-crypto: introduce akcipher
> > > > service
> > > >
> > > > On Tue, Jan 11, 2022 at 11:14:27AM +0800, 何磊 wrote:
> > > > > Hello virtio community,
> > > > >
> > > > > I’d like to request the TC vote on resolving the follow issue:
> > > > > Enhancement: https://github.com/oasis-tcs/virtio-spec/issues/129
> > > >
> > > > Does not look like we have a lot of response with this, and it seems
> > > > risky to add this now since spec freeze is imminent.
> > > > I think the right way to do it is to submit the supporting patches
> > > > to the linux kernel and probably qemu.
> > > > A bunch of crypto experts on the linux mailing list.
> > > >
> > > > In particular I note that virtio crypto already has a ton of
> > > > features that don't seem to be supported by the linux driver or
> > > > qemu. Kind of reluctant to add more without some review from developers
> > implementing this.
> > > >
> > > >
> > > Hi Michael,
> > >
> > > I can't agree more with you. Eg. the virtio crypto doesn't support
> > > stateless mode currently in linux and qemu upstream lthough this
> > > virtio crypto spec already supports. If we expand the specification in firstly, it
> > may make it more difficult to maintain in the future.
> > >
> > > Regards,
> > > -Gonglei
> >
> >
> > So what's the plan with stateless btw? why isn't it used? is it completely useless?
> > why do we have it in the spec?
> >
>
> The stateless mode is valuable in short connection encryption scenarios.
> It does not need to create sessions which is proposed by Stefan IIRC.
>
> Actually, we completed a demo before, but the demo was not pushed to the community
> due to other arrangements in the company projects. When we find a gap, we'll push it again. :)
>
> Regards,
> -Gonglei
Right. IOW it was added to spec too early. Can you review the
akcipher spec proposal meanwhile?
--
MST
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/
prev parent reply other threads:[~2022-01-20 10:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-10 12:53 [virtio-comment] [V3 PATCH 0/1] Introduce virtio asymmetric crypto service Lei He
2021-12-10 12:53 ` [virtio-comment] [V3 PATCH 1/1] virtio-crypto: introduce akcipher service Lei He
2021-12-21 2:40 ` [virtio-comment] PING: " 何磊
2022-06-17 10:21 ` Michael S. Tsirkin
2022-06-17 11:55 ` [virtio-comment] Re: [External] " 何磊
2022-01-10 12:20 ` 何磊
2022-01-10 12:55 ` [virtio-comment] " Michael S. Tsirkin
2022-01-15 17:37 ` Michael S. Tsirkin
2022-01-16 7:18 ` [virtio-comment] Re: [Phishing Risk] [External] " 何磊
2022-01-11 3:14 ` [virtio-comment] " 何磊
2022-01-19 15:17 ` Michael S. Tsirkin
[not found] ` <3bc3a06782b943e8a43b07954ba328fd@huawei.com>
2022-01-20 7:26 ` Michael S. Tsirkin
[not found] ` <46e69803beeb4741a33c89e2351370ab@huawei.com>
2022-01-20 10:47 ` Michael S. Tsirkin [this message]
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=20220120054600-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=arei.gonglei@huawei.com \
--cc=helei.sig11@bytedance.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 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.