From: Akhil Goyal <akhil.goyal@nxp.com>
To: dev@dpdk.org
Cc: stable@dpdk.org, konstantin.ananyev@intel.com,
radu.nicolau@intel.com, Vakul Garg <vakul.garg@nxp.com>
Subject: [dpdk-stable] [PATCH] examples/ipsec-secgw: fix SHA256-HMAC digest length
Date: Wed, 6 Nov 2019 15:23:22 +0530 [thread overview]
Message-ID: <20191106095322.25881-1-akhil.goyal@nxp.com> (raw)
From: Vakul Garg <vakul.garg@nxp.com>
As per RFC4868, SHA-256 should use 128 bits of ICV.
Fixes: b5350285ce6e ("examples/ipsec-secgw: support SHA256 HMAC")
Cc: stable@dpdk.org
Signed-off-by: Vakul Garg <vakul.garg@nxp.com>
Acked-by: Akhil Goyal <akhil.goyal@nxp.com>
---
examples/ipsec-secgw/sa.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/examples/ipsec-secgw/sa.c b/examples/ipsec-secgw/sa.c
index 4cb90857c..d0ae8ac9a 100644
--- a/examples/ipsec-secgw/sa.c
+++ b/examples/ipsec-secgw/sa.c
@@ -115,7 +115,7 @@ const struct supported_auth_algo auth_algos[] = {
{
.keyword = "sha256-hmac",
.algo = RTE_CRYPTO_AUTH_SHA256_HMAC,
- .digest_len = 12,
+ .digest_len = 16,
.key_len = 32
}
};
--
2.17.1
next reply other threads:[~2019-11-06 10:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-06 9:53 Akhil Goyal [this message]
2019-11-06 13:17 ` [dpdk-stable] [dpdk-dev] " Akhil Goyal
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=20191106095322.25881-1-akhil.goyal@nxp.com \
--to=akhil.goyal@nxp.com \
--cc=dev@dpdk.org \
--cc=konstantin.ananyev@intel.com \
--cc=radu.nicolau@intel.com \
--cc=stable@dpdk.org \
--cc=vakul.garg@nxp.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).