> -----Original Message----- > From: De Lara Guarch, Pablo > Sent: Tuesday, July 25, 2017 6:25 AM > To: zbigniew.bo...@caviumnetworks.com; > jerin.ja...@caviumnetworks.com; akhil.go...@nxp.com; > hemant.agra...@nxp.com; Trahe, Fiona <fiona.tr...@intel.com>; Jain, > Deepak K <deepak.k.j...@intel.com>; Griffin, John > <john.grif...@intel.com>; Doherty, Declan <declan.dohe...@intel.com> > Cc: dev@dpdk.org; De Lara Guarch, Pablo > <pablo.de.lara.gua...@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
