From: Pablo de Lara <pablo.de.lara.guarch@intel.com>
To: roy.fan.zhang@intel.com, vvelumuri@marvell.com
Cc: dev@dpdk.org, Pablo de Lara <pablo.de.lara.guarch@intel.com>
Subject: [dpdk-dev] [PATCH] test/crypto: fix test vectors for ZUC-256
Date: Sun, 31 Oct 2021 22:04:21 +0000 [thread overview]
Message-ID: <20211031220421.52181-1-pablo.de.lara.guarch@intel.com> (raw)
Fix the IV for ZUC-256 test vectors
Fixes: 216125c62d28 ("test/crypto: add ZUC-256 vectors")
Signed-off-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
---
app/test/test_cryptodev_zuc_test_vectors.h | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/app/test/test_cryptodev_zuc_test_vectors.h b/app/test/test_cryptodev_zuc_test_vectors.h
index ba5c68ca72..5c5bebebc3 100644
--- a/app/test/test_cryptodev_zuc_test_vectors.h
+++ b/app/test/test_cryptodev_zuc_test_vectors.h
@@ -1296,7 +1296,7 @@ static struct wireless_test_data zuc256_test_case_cipher_1 = {
.data = {
0x8e, 0x5d, 0xbc, 0x3f, 0xb9, 0xae, 0x66, 0xa3,
0xb9, 0x5c, 0x12, 0x14, 0xdb, 0xc5, 0xbc, 0x18,
- 0x48, 0x92, 0x09, 0x86, 0x65, 0xb3, 0x2e, 0x92,
+ 0x48, 0x12, 0x09, 0x06, 0x25, 0x33, 0x2e, 0x12,
0x12
},
.len = 25
@@ -1365,8 +1365,8 @@ static struct wireless_test_data zuc256_test_case_cipher_2 = {
.data = {
0x98, 0xcc, 0x89, 0x9f, 0xaf, 0x6d, 0x64, 0xb6,
0xb1, 0xe8, 0x21, 0x72, 0xee, 0xb6, 0xcc, 0xe3,
- 0xcf, 0xf2, 0x68, 0x61, 0xe1, 0x0d, 0x9e, 0xdc,
- 0x74
+ 0xcf, 0x32, 0x28, 0x21, 0x21, 0x0d, 0x1e, 0x1c,
+ 0x34
},
.len = 25
},
@@ -1464,8 +1464,8 @@ static struct wireless_test_data zuc256_test_case_auth_1 = {
.data = {
0xf5, 0x8d, 0x08, 0x26, 0x94, 0x14, 0xc7, 0x4d,
0xf5, 0x7c, 0x9c, 0xaa, 0x45, 0x53, 0xfd, 0x85,
- 0x23, 0x8b, 0xc0, 0x4e, 0xa6, 0x2b, 0xcf, 0x41,
- 0xe6
+ 0x23, 0x0b, 0x00, 0x0e, 0x26, 0x2b, 0x0f, 0x01,
+ 0x26
},
.len = 25
},
--
2.25.1
next reply other threads:[~2021-10-31 22:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-31 22:04 Pablo de Lara [this message]
2021-11-04 10:57 ` [dpdk-dev] [EXT] " 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=20211031220421.52181-1-pablo.de.lara.guarch@intel.com \
--to=pablo.de.lara.guarch@intel.com \
--cc=dev@dpdk.org \
--cc=roy.fan.zhang@intel.com \
--cc=vvelumuri@marvell.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).