From: "Longpeng (Mike)" <longpeng2@huawei.com>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: eblake@redhat.com, armbru@redhat.com, arei.gonglei@huawei.com,
qemu-devel@nongnu.org, wu.wubin@huawei.com,
jianjay.zhou@huawei.com
Subject: Re: [Qemu-devel] [PATCH for-2.9 1/2] crypto: add 3des-ede support when using libgcrypt/nettle
Date: Wed, 7 Dec 2016 17:46:21 +0800 [thread overview]
Message-ID: <5847DA6D.20404@huawei.com> (raw)
In-Reply-To: <20161207093702.GD21167@redhat.com>
Hi Daniel,
On 2016/12/7 17:37, Daniel P. Berrange wrote:
> On Wed, Dec 07, 2016 at 04:33:41PM +0800, Longpeng(Mike) wrote:
......
>> diff --git a/qapi/crypto.json b/qapi/crypto.json
>> index 5c9d7d4..848b6cd 100644
>> --- a/qapi/crypto.json
>> +++ b/qapi/crypto.json
>> @@ -63,6 +63,7 @@
>> # @aes-192: AES with 192 bit / 24 byte keys
>> # @aes-256: AES with 256 bit / 32 byte keys
>> # @des-rfb: RFB specific variant of single DES. Do not use except in VNC.
>> +# @3des-ede: 3DES-EDE with 192 bit / 24 byte keys
>
> Lets just call this '3des' as 'ede' is can be assumed, eg
>
> # @3des: 3DES (EDE) with 192 bit / 24 byte keys
>
Okay, I will fix it in V2, thanks. :)
>
> Regards,
> Daniel
--
Regards,
Longpeng(Mike)
next prev parent reply other threads:[~2016-12-07 9:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-07 8:33 [Qemu-devel] [PATCH for-2.9 0/2] crypto: add 3des-ede support Longpeng(Mike)
2016-12-07 8:33 ` [Qemu-devel] [PATCH for-2.9 1/2] crypto: add 3des-ede support when using libgcrypt/nettle Longpeng(Mike)
2016-12-07 8:52 ` Gonglei (Arei)
2016-12-07 9:19 ` Longpeng (Mike)
2016-12-07 9:21 ` Longpeng (Mike)
2016-12-07 9:43 ` Daniel P. Berrange
2016-12-07 9:37 ` Daniel P. Berrange
2016-12-07 9:46 ` Longpeng (Mike) [this message]
2016-12-07 8:33 ` [Qemu-devel] [PATCH for-2.9 2/2] cryptodev: add 3des-ede support Longpeng(Mike)
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=5847DA6D.20404@huawei.com \
--to=longpeng2@huawei.com \
--cc=arei.gonglei@huawei.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=eblake@redhat.com \
--cc=jianjay.zhou@huawei.com \
--cc=qemu-devel@nongnu.org \
--cc=wu.wubin@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).