From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 7608EA054F; Tue, 18 Feb 2020 10:45:55 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id B035E1D8D9; Tue, 18 Feb 2020 10:45:54 +0100 (CET) Received: from mx0b-0016f401.pphosted.com (mx0b-0016f401.pphosted.com [67.231.156.173]) by dpdk.org (Postfix) with ESMTP id 042E71D8D6 for ; Tue, 18 Feb 2020 10:45:52 +0100 (CET) Received: from pps.filterd (m0045851.ppops.net [127.0.0.1]) by mx0b-0016f401.pphosted.com (8.16.0.42/8.16.0.42) with SMTP id 01I9jS8V028710; Tue, 18 Feb 2020 01:45:52 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=marvell.com; h=from : to : cc : subject : date : message-id : mime-version : content-transfer-encoding : content-type; s=pfpt0818; bh=jDwM9tppBSVTq0s5ELCHHf579ODGoND0V+95WgYR++4=; b=imnPNKklKRqbmp+CXBgcGYiO7uJs3SoZwI7UyhW8UFWsXGO94nBQQLYqJiXYEU5Q5pUP YzQzSI1w6R1bQ4D/qAkPgoFotZdgSkbUyvrKeekCFKwondknlm5TkJjj458raKZ7PqrN TeJ60AIsSyW/3tvBQ81fXK9xcfKt8DuScVSxsaPVX9WmL+j0EhCjeMh36oRMRKbJ1zDV d/O8rBpOORcfQDqYawfghCC3gYrN4VaG73SRO0rah3+Teys+nFztb07iiVptJk220LRV HdpS8wIlECuQQoFxFTvjwUMORTAzaSpPgdxjUxKHKLnRH68A9bnvKNZS/Qt5nAzhMexm 4Q== Received: from sc-exch03.marvell.com ([199.233.58.183]) by mx0b-0016f401.pphosted.com with ESMTP id 2y6h1t2des-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Tue, 18 Feb 2020 01:45:52 -0800 Received: from DC5-EXCH02.marvell.com (10.69.176.39) by SC-EXCH03.marvell.com (10.93.176.83) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Tue, 18 Feb 2020 01:45:50 -0800 Received: from SC-EXCH03.marvell.com (10.93.176.83) by DC5-EXCH02.marvell.com (10.69.176.39) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Tue, 18 Feb 2020 01:45:49 -0800 Received: from maili.marvell.com (10.93.176.43) by SC-EXCH03.marvell.com (10.93.176.83) with Microsoft SMTP Server id 15.0.1497.2 via Frontend Transport; Tue, 18 Feb 2020 01:45:48 -0800 Received: from ajoseph83.caveonetworks.com (ajoseph83.caveonetworks.com [10.29.45.60]) by maili.marvell.com (Postfix) with ESMTP id D08083F703F; Tue, 18 Feb 2020 01:45:46 -0800 (PST) From: Anoob Joseph To: Marko Kovacevic , Akhil Goyal , David Marchand CC: Anoob Joseph , Fan Zhang , Narayana Prasad , Date: Tue, 18 Feb 2020 15:14:35 +0530 Message-ID: <1582019075-7932-1-git-send-email-anoobj@marvell.com> X-Mailer: git-send-email 2.7.4 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.138, 18.0.572 definitions=2020-02-18_02:2020-02-17, 2020-02-18 signatures=0 Subject: [dpdk-dev] [PATCH] examples/fips_validation: fix incorrect CT length string X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" The NIST test vectors use the string 'PTlen' to denote text lengths in case of encrypt & decrypt operations. So the same string need to be used while parsing PT and CT. Fixes: 12f826533ff7 ("examples/fips_validation: fix incorrect string for CT length") Signed-off-by: Anoob Joseph --- examples/fips_validation/fips_validation_gcm.c | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/examples/fips_validation/fips_validation_gcm.c b/examples/fips_validation/fips_validation_gcm.c index bc2d37d..47576e9 100644 --- a/examples/fips_validation/fips_validation_gcm.c +++ b/examples/fips_validation/fips_validation_gcm.c @@ -19,7 +19,6 @@ #define PTLEN_STR "PTlen = " #define AADLEN_STR "AADlen = " #define TAGLEN_STR "Taglen = " -#define CTLEN_STR "CTlen = " #define COUNT_STR "Count = " #define KEY_STR "Key = " @@ -47,7 +46,10 @@ struct fips_test_callback gcm_interim_vectors[] = { {KEYLEN_STR, parser_read_uint32_bit_val, &vec.aead.key}, {IVLEN_STR, parser_read_uint32_bit_val, &vec.iv}, {PTLEN_STR, parser_read_uint32_bit_val, &vec.pt}, - {CTLEN_STR, parser_read_uint32_bit_val, &vec.ct}, + {PTLEN_STR, parser_read_uint32_bit_val, &vec.ct}, + /**< The NIST test vectors use 'PTlen' to denote input text + * length in case of decrypt & encrypt operations. + */ {AADLEN_STR, parser_read_uint32_bit_val, &vec.aead.aad}, {TAGLEN_STR, parser_read_uint32_bit_val, &vec.aead.digest}, -- 2.7.4