From: "Daniel P. Berrange" <berrange@redhat.com>
To: "Gonglei (Arei)" <arei.gonglei@huawei.com>
Cc: longpeng <longpeng2@huawei.com>,
"eblake@redhat.com" <eblake@redhat.com>,
"armbru@redhat.com" <armbru@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"Wubin (H)" <wu.wubin@huawei.com>,
"Zhoujian (jay, Euler)" <jianjay.zhou@huawei.com>
Subject: Re: [Qemu-devel] [PATCH for-2.9 1/3] crypto: add standard des support
Date: Mon, 5 Dec 2016 16:59:05 +0000 [thread overview]
Message-ID: <20161205165905.GR2498@redhat.com> (raw)
In-Reply-To: <33183CC9F5247A488A2544077AF19020DA152B60@DGGEMA505-MBX.china.huawei.com>
On Mon, Dec 05, 2016 at 09:29:59AM +0000, Gonglei (Arei) wrote:
> >
> > > switch (alg) {
> > > + case QCRYPTO_CIPHER_ALG_DES:
> > > case QCRYPTO_CIPHER_ALG_DES_RFB:
> > > case QCRYPTO_CIPHER_ALG_AES_128:
> > > case QCRYPTO_CIPHER_ALG_AES_192:
> > > @@ -256,11 +257,17 @@ QCryptoCipher
> > *qcrypto_cipher_new(QCryptoCipherAlgorithm alg,
> > > ctx = g_new0(QCryptoCipherNettle, 1);
> > >
> > > switch (alg) {
> > > + case QCRYPTO_CIPHER_ALG_DES:
> > > case QCRYPTO_CIPHER_ALG_DES_RFB:
> > > ctx->ctx = g_new0(struct des_ctx, 1);
> > > - rfbkey = qcrypto_cipher_munge_des_rfb_key(key, nkey);
> > > - des_set_key(ctx->ctx, rfbkey);
> > > - g_free(rfbkey);
> > > +
> > > + if (alg == QCRYPTO_CIPHER_ALG_DES_RFB) {
> > > + rfbkey = qcrypto_cipher_munge_des_rfb_key(key, nkey);
> > > + des_set_key(ctx->ctx, rfbkey);
> > > + g_free(rfbkey);
> > > + } else {
> > > + des_set_key(ctx->ctx, key);
> > > + }
> > >
> > > ctx->alg_encrypt_native = des_encrypt_native;
> > > ctx->alg_decrypt_native = des_decrypt_native;
> > > diff --git a/crypto/cipher.c b/crypto/cipher.c
> > > index a9bca41..00d9682 100644
> > > --- a/crypto/cipher.c
> > > +++ b/crypto/cipher.c
> > > @@ -27,6 +27,7 @@ static size_t
> > alg_key_len[QCRYPTO_CIPHER_ALG__MAX] = {
> > > [QCRYPTO_CIPHER_ALG_AES_128] = 16,
> > > [QCRYPTO_CIPHER_ALG_AES_192] = 24,
> > > [QCRYPTO_CIPHER_ALG_AES_256] = 32,
> > > + [QCRYPTO_CIPHER_ALG_DES] = 8,
> > > [QCRYPTO_CIPHER_ALG_DES_RFB] = 8,
> > > [QCRYPTO_CIPHER_ALG_CAST5_128] = 16,
> > > [QCRYPTO_CIPHER_ALG_SERPENT_128] = 16,
> > > @@ -41,6 +42,7 @@ static size_t
> > alg_block_len[QCRYPTO_CIPHER_ALG__MAX] = {
> > > [QCRYPTO_CIPHER_ALG_AES_128] = 16,
> > > [QCRYPTO_CIPHER_ALG_AES_192] = 16,
> > > [QCRYPTO_CIPHER_ALG_AES_256] = 16,
> > > + [QCRYPTO_CIPHER_ALG_DES] = 8,
> > > [QCRYPTO_CIPHER_ALG_DES_RFB] = 8,
> > > [QCRYPTO_CIPHER_ALG_CAST5_128] = 8,
> > > [QCRYPTO_CIPHER_ALG_SERPENT_128] = 16,
> > > @@ -107,7 +109,8 @@
> > qcrypto_cipher_validate_key_length(QCryptoCipherAlgorithm alg,
> > > }
> > >
> > > if (mode == QCRYPTO_CIPHER_MODE_XTS) {
> > > - if (alg == QCRYPTO_CIPHER_ALG_DES_RFB) {
> > > + if (alg == QCRYPTO_CIPHER_ALG_DES_RFB
> > > + || alg == QCRYPTO_CIPHER_ALG_DES) {
> > > error_setg(errp, "XTS mode not compatible with DES-RFB");
> > > return false;
> > > }
> > > diff --git a/qapi/crypto.json b/qapi/crypto.json
> > > index 5c9d7d4..d403ab9 100644
> > > --- a/qapi/crypto.json
> > > +++ b/qapi/crypto.json
> > > @@ -75,7 +75,7 @@
> > > { 'enum': 'QCryptoCipherAlgorithm',
> > > 'prefix': 'QCRYPTO_CIPHER_ALG',
> > > 'data': ['aes-128', 'aes-192', 'aes-256',
> > > - 'des-rfb',
> > > + 'des-rfb', 'des',
> >
> > Can we call this '3des' to make it clear that this is Triple-DES and not
> > the single-DES (which des-rfb is)
> >
> Actually the current des is not triple-DES, just the single-DES, and des-rfb in QEMU is just a variant of
> single DES, which change the standard key by calling qcrypto_cipher_munge_des_rfb_key().
>
> I think we can add the 3des support as well in the next step.
>
> The current single-DES in the patch set is ok to me. :)
Per my othre reply in this thread, I don't think we should be supporting
single-DES at all in QEMU / cryptodev. So IMHO, the correct fix is to
remove the single-DES support from cryptodev entirely
Regards,
Daniel
--
|: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org -o- http://virt-manager.org :|
|: http://entangle-photo.org -o- http://search.cpan.org/~danberr/ :|
next prev parent reply other threads:[~2016-12-05 16:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-05 8:59 [Qemu-devel] [PATCH for-2.9 0/3] crypto: add standard des support Longpeng(Mike)
2016-12-05 8:59 ` [Qemu-devel] [PATCH for-2.9 1/3] " Longpeng(Mike)
2016-12-05 9:18 ` Daniel P. Berrange
2016-12-05 9:29 ` Gonglei (Arei)
2016-12-05 16:59 ` Daniel P. Berrange [this message]
2016-12-06 1:23 ` Gonglei (Arei)
2016-12-06 9:21 ` Daniel P. Berrange
2016-12-06 9:28 ` Gonglei (Arei)
2016-12-05 11:11 ` Longpeng (Mike)
2016-12-05 11:18 ` Daniel P. Berrange
2016-12-05 19:15 ` Eric Blake
2016-12-07 0:58 ` Longpeng (Mike)
2016-12-05 8:59 ` [Qemu-devel] [PATCH for-2.9 2/3] cryptodev: switch to standard des Longpeng(Mike)
2016-12-05 9:25 ` Daniel P. Berrange
2016-12-05 8:59 ` [Qemu-devel] [PATCH for-2.9 3/3] tests: crypto: add testcase for standard des(ecb) Longpeng(Mike)
2016-12-05 9:24 ` Daniel P. Berrange
2016-12-05 9:46 ` 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=20161205165905.GR2498@redhat.com \
--to=berrange@redhat.com \
--cc=arei.gonglei@huawei.com \
--cc=armbru@redhat.com \
--cc=eblake@redhat.com \
--cc=jianjay.zhou@huawei.com \
--cc=longpeng2@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).