From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: "zbigniew.bodek@caviumnetworks.com"
<zbigniew.bodek@caviumnetworks.com>,
"jerin.jacob@caviumnetworks.com" <jerin.jacob@caviumnetworks.com>,
"akhil.goyal@nxp.com" <akhil.goyal@nxp.com>,
"hemant.agrawal@nxp.com" <hemant.agrawal@nxp.com>,
"Trahe, Fiona" <fiona.trahe@intel.com>,
"Jain, Deepak K" <deepak.k.jain@intel.com>,
"Griffin, John" <john.griffin@intel.com>,
"Doherty, Declan" <declan.doherty@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 0/3] HMAC supported key size fixes
Date: Thu, 27 Jul 2017 14:40:23 +0000 [thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D8976CBE3757@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <20170725052457.43952-1-pablo.de.lara.guarch@intel.com>
> -----Original Message-----
> From: De Lara Guarch, Pablo
> Sent: Tuesday, July 25, 2017 6:25 AM
> To: zbigniew.bodek@caviumnetworks.com;
> jerin.jacob@caviumnetworks.com; akhil.goyal@nxp.com;
> hemant.agrawal@nxp.com; Trahe, Fiona <fiona.trahe@intel.com>; Jain,
> Deepak K <deepak.k.jain@intel.com>; Griffin, John
> <john.griffin@intel.com>; Doherty, Declan <declan.doherty@intel.com>
> Cc: dev@dpdk.org; De Lara Guarch, Pablo
> <pablo.de.lara.guarch@intel.com>
> Subject: [PATCH 0/3] HMAC supported key size fixes
>
> For HMAC algorithms (SHAx/MD5), the capabilities were not correct, as
> they were just a fixed value (block size).
> Instead, the authentication key size for these algorithms can go between 1
> and the block size.
>
> Note that these patches are fixing AESNI-MB, OpenSSL and QAT PMDs, but
> DPAA2 and ARMv8 crypto PMDs might need these fixes too.
>
> Pablo de Lara (3):
> crypto/aesni_mb: fix HMAC supported key sizes
> crypto/openssl: fix HMAC supported key sizes
> crypto/qat: fix HMAC supported key sizes
>
> drivers/crypto/aesni_mb/rte_aesni_mb_pmd_ops.c | 24 ++++++++++++--
> ----------
> drivers/crypto/openssl/rte_openssl_pmd_ops.c | 24 ++++++++++++-------
> -----
> drivers/crypto/qat/qat_crypto_capabilities.h | 24 ++++++++++++-----------
> -
> 3 files changed, 36 insertions(+), 36 deletions(-)
>
> --
> 2.9.4
Applied to dpdk-next-crypto.
Pablo
prev parent reply other threads:[~2017-07-27 14:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-25 5:24 Pablo de Lara
2017-07-25 5:24 ` [dpdk-dev] [PATCH 1/3] crypto/aesni_mb: fix HMAC supported key sizes Pablo de Lara
2017-07-27 10:22 ` Declan Doherty
2017-07-25 5:24 ` [dpdk-dev] [PATCH 2/3] crypto/openssl: " Pablo de Lara
2017-07-27 10:21 ` Declan Doherty
2017-07-25 5:24 ` [dpdk-dev] [PATCH 3/3] crypto/qat: " Pablo de Lara
2017-07-27 9:54 ` Trahe, Fiona
2017-07-27 11:54 ` [dpdk-dev] [PATCH] crypto/dpaa2_sec: " Akhil Goyal
2017-07-27 13:57 ` Hemant Agrawal
2017-07-27 14:25 ` De Lara Guarch, Pablo
2017-07-27 14:40 ` De Lara Guarch, Pablo [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=E115CCD9D858EF4F90C690B0DCB4D8976CBE3757@IRSMSX108.ger.corp.intel.com \
--to=pablo.de.lara.guarch@intel.com \
--cc=akhil.goyal@nxp.com \
--cc=declan.doherty@intel.com \
--cc=deepak.k.jain@intel.com \
--cc=dev@dpdk.org \
--cc=fiona.trahe@intel.com \
--cc=hemant.agrawal@nxp.com \
--cc=jerin.jacob@caviumnetworks.com \
--cc=john.griffin@intel.com \
--cc=zbigniew.bodek@caviumnetworks.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).