From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 59E8FA04FF for ; Tue, 24 May 2022 11:13:56 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 2B5DC4067B; Tue, 24 May 2022 11:13:56 +0200 (CEST) Received: from mga12.intel.com (mga12.intel.com [192.55.52.136]) by mails.dpdk.org (Postfix) with ESMTP id 98E8F400D6 for ; Tue, 24 May 2022 11:13:54 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1653383634; x=1684919634; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=q8rF4bQsPLQeaYSCEPFTNsst1wolIdv7el0oUUbj8tw=; b=AhM1/EhmTb5gNdcvrWDDBNL8nWw38aH55V6VQfkYRJ6uQTVZ55S0LiwF LZUyd4KoSkmRr/TkhPwf4oaX3w/J3isFCYLSvxqlWRjRcwrxcJKY2fJ90 LmWLHRizst+n9I+MoxJ+perOw6WBdjSlf3rOw3+USviOZwwXCPYLOZwlG hacxkALyOeFQJfGZd3XLZYZU78o6MP6U2KkfADUud8Iq5srT0Et0e3wKx CxbYQk/m6Ww/hBB+MAEesDe72gRc3dc3x/kf4m0KW7ibgt6tU28iZUrSe yCdrZNpRlu7PVPdMSLFiK9JluO17zCZd0Du2+97cBFBh1DtZ1zUeGCd+Q A==; X-IronPort-AV: E=McAfee;i="6400,9594,10356"; a="253351843" X-IronPort-AV: E=Sophos;i="5.91,248,1647327600"; d="scan'208,217";a="253351843" Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by fmsmga106.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 24 May 2022 02:13:53 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.91,248,1647327600"; d="scan'208,217";a="663833078" Received: from orsmsx605.amr.corp.intel.com ([10.22.229.18]) by FMSMGA003.fm.intel.com with ESMTP; 24 May 2022 02:13:53 -0700 Received: from orsmsx610.amr.corp.intel.com (10.22.229.23) by ORSMSX605.amr.corp.intel.com (10.22.229.18) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2308.27; Tue, 24 May 2022 02:13:52 -0700 Received: from ORSEDG601.ED.cps.intel.com (10.7.248.6) by orsmsx610.amr.corp.intel.com (10.22.229.23) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2308.27 via Frontend Transport; Tue, 24 May 2022 02:13:52 -0700 Received: from NAM11-DM6-obe.outbound.protection.outlook.com (104.47.57.175) by edgegateway.intel.com (134.134.137.102) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2308.27; Tue, 24 May 2022 02:13:52 -0700 ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=W6c7yWM8wSppd+QfWH0UJ04IMEE0qHeBRM3L3Lc4ZaftSNw7eOTVRafxuh8R793Yh6vT3ZlNZMQ1789afmc9HcJMgIKM3UjkJFWLE8pfxbsdUWa5Xc1B7ilz7NqgbeJHyyYWwC85HI+k36OqwX4T/6SsWGieg9Klrrpt21SDmv43vh2G3rBeECQEW+WXJV5BdQNZztopr9KyDdQfqJWZkE6ebrUifVIqRY9zxDPjXSLpgdVTjypCESqi9wKyndK3rb1DFCpuFtvVw8hZhCcJPLpURtdNuw1y8IiswZELwrQhH5dYWoI7v624ac2Io4gT1pIFosmzzKtH2/vsjxG7Xw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=yLF5qYQa0hELa2lL+aLuyeFaD13BWdt6X6aRTqoD7jU=; b=KRcYC4/K2PBLLObJGzrN6A+vbp8nFYkJ/+5YvY4guoRZv1KQwwHaCk+gcNy6g8b4daTciagzhCDjmbl2mRLenfNLaF/O6uZE6Yr45T+Ig94Fuipo78ci8YD6+we/9ZlA+ppClJjKCaPLCPvy1rEpu94RmLjuZ0D0d5EEYjsEosTX9ULzYqc2oge/PVsLvQ9Tg8fVOEfGzC086LJLgHyu1IlYwHT2VtvDf6KDJlTag+APwb8A1ZwJBrd6Ls+Kzq98pGREv9ol+wvvSJmZuObIOYCa4/RTRhjDjP0l36kTUI8GrrbqTdszafZjlBFCFSeHp4q7uzFb9nF28EPrinOOkA== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=intel.com; dmarc=pass action=none header.from=intel.com; dkim=pass header.d=intel.com; arc=none Received: from PH0PR11MB5013.namprd11.prod.outlook.com (2603:10b6:510:30::21) by MN2PR11MB4463.namprd11.prod.outlook.com (2603:10b6:208:190::25) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.5273.15; Tue, 24 May 2022 09:13:50 +0000 Received: from PH0PR11MB5013.namprd11.prod.outlook.com ([fe80::fc0f:1644:98b5:be1]) by PH0PR11MB5013.namprd11.prod.outlook.com ([fe80::fc0f:1644:98b5:be1%5]) with mapi id 15.20.5273.023; Tue, 24 May 2022 09:13:50 +0000 From: "Kusztal, ArkadiuszX" To: Balakrishnan K , "users@dpdk.org" Subject: RE: how to use crypto openssl PMD for asymmetric encryption and decryption Thread-Topic: how to use crypto openssl PMD for asymmetric encryption and decryption Thread-Index: Adhul7L76HpVKxCxQgm6OmL7h9++VgACBMowACMLKYAACHjIQA== Date: Tue, 24 May 2022 09:13:50 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: msip_labels: MSIP_Label_5cbf6393-50e2-4904-bc3e-1804619f2b03_ActionId=1e9b2051-9f45-4073-b7f5-e6b509538b52; MSIP_Label_5cbf6393-50e2-4904-bc3e-1804619f2b03_ContentBits=0; MSIP_Label_5cbf6393-50e2-4904-bc3e-1804619f2b03_Enabled=true; MSIP_Label_5cbf6393-50e2-4904-bc3e-1804619f2b03_Method=Privileged; MSIP_Label_5cbf6393-50e2-4904-bc3e-1804619f2b03_Name=General-Test; MSIP_Label_5cbf6393-50e2-4904-bc3e-1804619f2b03_SetDate=2022-05-23T11:32:59Z; MSIP_Label_5cbf6393-50e2-4904-bc3e-1804619f2b03_SiteId=20210462-2c5e-4ec8-b3e2-0be950f292ca; dlp-reaction: no-action dlp-version: 11.6.500.17 dlp-product: dlpe-windows authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=intel.com; x-ms-publictraffictype: Email x-ms-office365-filtering-correlation-id: ae83d1a9-4aa0-4070-aeea-08da3d65b75d x-ms-traffictypediagnostic: MN2PR11MB4463:EE_ x-microsoft-antispam-prvs: x-ms-exchange-senderadcheck: 1 x-ms-exchange-antispam-relay: 0 x-microsoft-antispam: BCL:0; x-microsoft-antispam-message-info: acA0Mif/Uwo1TxOTQpU+hPkw8ecUV7efdVWi0x/N/vcvlwl3dFlZ3lLcVWCkCpDpMfRgEwsCBEytL2DJCCAZP0PNA2t8LNErlgLr45+rU7p0Cu5mFvhBWQ8tV2XAEbCzS0CZD2LyuRCPR1oK2di40WOsH4Hv8oYl45iGUABUoTnaa8AiBp5a4x9UpJ03hrLYHIWjhBisZx4CDcsLwt/+nc21gUuolau1JcwKMPHvPxCQU1QU44BShKZ0k5z1WYjzRt+YiXFp/wLp7np0gTEySIkgjcUwLLqB29qn878zfsSgr+CDYmPrE1teDTweXQ1ucHUd+HCqJgbqV7osLYON6d/EVOgIMx6HBEFrNtQEMWqW2xzYiro4HlW4jQNj3VZfE6vvOcLUVNfj8BtB8RgBRjcdXBYWKOBnxLukD8DqLvuNOFjn3Wv2yHdA932vXbt6W7dl2X5I1CoHUaxlblX5ErC3pbH0EyRgyr9CFFRJPsuviZeOnp08sk2AwvUWJhh9Xd3ZwvNCYXmn6HLckwqNNGtF5gxZ/RqJ8a5XsNkV0ZRKU+YHxOWYY+77YUCanv1f071CpFSXxMoqxbpg1G84pyfeko+vlx3MVsCoOD1ivjS/EePDOIdlIxeCRtPoixaAbbwx/PSKvtBF6GVXt2nibqENBjl383YyHH77SR5hujWTDOcJgNV3vWw7HbFM5tFWI6CfbGjcItflAkiF9mlDkoGrdg4X6AZ9rqswS9fEYpH3+iYRdvYaA/X7KTvEBrL6HGj0JCNopbsrz5WLkIus0C1W4C1dy4VxJV8O6H3kTtk= x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:PH0PR11MB5013.namprd11.prod.outlook.com; PTR:; CAT:NONE; SFS:(13230001)(366004)(83380400001)(186003)(66476007)(82960400001)(166002)(55016003)(38100700002)(122000001)(38070700005)(6506007)(7696005)(66556008)(64756008)(71200400001)(110136005)(966005)(76116006)(66446008)(316002)(2906002)(508600001)(66946007)(26005)(8676002)(53546011)(5660300002)(52536014)(21615005)(9686003)(33656002)(8936002)(86362001); DIR:OUT; SFP:1102; x-ms-exchange-antispam-messagedata-chunkcount: 1 x-ms-exchange-antispam-messagedata-0: =?us-ascii?Q?rUYw5KiFLgcMBqrSRF0ztZ6LPKOe8QRxK3/y8fUGA907Wa1yGY0Jl1J459H8?= =?us-ascii?Q?CcX5AmXa+Y6NIkIzHLOKWjyMrICsLHaFmpw5wVc2IjriuLTbTlcmMCSnhhn1?= =?us-ascii?Q?SObG793Uou58JRGWsPBHkU3VhN1LEsITq0ESeL3mVwjtT3b9+A6xSTHSE+AS?= =?us-ascii?Q?rj1hZJRuLlGBWI6gvd+cCvfmHOGrYFJG9DrWfDyTKI/6Z0SSyaSM2DUH7SFt?= =?us-ascii?Q?tNM4za0KLBvLV0KfsMBnJHPUDyGJcjavX26SxyVl26o2DFRWGoThqo9joBB6?= =?us-ascii?Q?MG5rRc/KROps1EsVYqP8afY3ijGAtMDlAjRMuqHpjkWsE5VW/0qzMwJgVq0Q?= =?us-ascii?Q?0A+4moMT/n+l7G+QP+271GNvAngjSic4K4zy/FOlPtaj3P0FbBnSDVmOd7v6?= =?us-ascii?Q?vINmmuW4L5a44PAG6KFwTAH32c4dqf4UfhABHU5CFD0XJolmKahkKxlpUtHR?= =?us-ascii?Q?w++PdG5W72mtFm2X20MxEBCS5BfXftntc/1efoip2IuJzdylxIq/Ijkf20Zj?= =?us-ascii?Q?oPje8+BGHJx2pirU5V2ESf3b3ooav/TYPnOWfO1iebSMM1MN8ODxHqU9KST/?= =?us-ascii?Q?6KvWQpxtpvsv/kL9e3tfC9Tjt3Kz3ETk73GYrMAIiQbi3UP6EGnGS7FWfphj?= =?us-ascii?Q?2Zzoo8s5UU2b+gWSKnvzEN1QDZPAjLkSzl9CI66/2edIiftGOQoZqwEm7dDr?= =?us-ascii?Q?MMJccYV1xKREqeV1ujr+cyZm8ewzJUSfVpxooZbXAJzgUxQQvUunPvt791Z5?= =?us-ascii?Q?JEJFb3NEJBynw9Mk2SKzweRTM/XUiBtQjKNNg6N7+RlMDS0+LJzqgP5LXApH?= =?us-ascii?Q?F0WuAXxqC3ESDfvKxbNXMdDdRyMAEq20CFrDp6CA7FnaVCIzYz6tQJAGUjp/?= =?us-ascii?Q?aPMNvDjVXsWdwULFbeZMJEYe/1G8R6pnBVNiVdQMPuXV/NXU8GyTmdoIDF52?= =?us-ascii?Q?/4Nh33fs2dovyc6lXIOOjILYhkuA3hnyYUUNLNoghXkbf+8DWv/PKT20+M+u?= =?us-ascii?Q?U7WDDbdcqvxTAglHP5PVz3mIRJC6UP9QG+HNtmjUuJBeZ53231XMd185yTMI?= =?us-ascii?Q?lB+/iijSojqNPUCA+umOFUjvGQmK5H/EiZT01Se/MzoVrCJK/iizzec1Qk+a?= =?us-ascii?Q?vfwu6zmySa9I6m9KOH6iEP2PH/ajfGBVFmIg44Icnswj/cLVtG6ImBySkvXH?= =?us-ascii?Q?LPP3j00payPrtW8Z5ipnC2auZpgm/Dd0iatJ5apJDbyZfFGPip79jgC+B5mJ?= =?us-ascii?Q?bFdWumg/EqNeJwbe974Ex94azfuL7AYlGH0x0gJYFHhWc68aSKoI0YGItr4w?= =?us-ascii?Q?kHMyBTIS87pw6FxLOr92XtkAr+OgODwQroomcnjLalmGpWsmLT28sioL34Rp?= =?us-ascii?Q?RxOxaV1bSBdIj65+weY5+kDm2NZLgwesg4tXMJKXJoR3ERjkCUDqJzhHJhTi?= =?us-ascii?Q?rWJZujVRCcP1pOZW0d+oDeUWkUrdSdmAwiqrAXgNt9yjtD/gMwet8GKvmGF6?= =?us-ascii?Q?4dbW8Jk6Jx/QeWarxcOh8MbWA5uw2Ygr1FnNVurzbR1TnE9aOoKdt7+Ap4kO?= =?us-ascii?Q?aGnGjL2n4wYiTisocUtSZOKwpRwI3tlYV4ldvT2x9gl4gvJHkHa/6KsatiZ4?= =?us-ascii?Q?HlENi2ynL+pSxl7XGam4Q5FOV/iMXpcmJzZOqU791OVoS/3DiyeqAHZJSOvP?= =?us-ascii?Q?JHAIKLD2JA2GJKqy9QMxyjvCrk6eAIemjZTmBSeYN5XoXtkTOPTE6SocZxYZ?= =?us-ascii?Q?X66cOD+S7dcKUGb3YP3ddtzCf70l5jg=3D?= Content-Type: multipart/alternative; boundary="_000_PH0PR11MB5013E6CD6BD9C5F4A6CDD1BB9FD79PH0PR11MB5013namp_" MIME-Version: 1.0 X-MS-Exchange-CrossTenant-AuthAs: Internal X-MS-Exchange-CrossTenant-AuthSource: PH0PR11MB5013.namprd11.prod.outlook.com X-MS-Exchange-CrossTenant-Network-Message-Id: ae83d1a9-4aa0-4070-aeea-08da3d65b75d X-MS-Exchange-CrossTenant-originalarrivaltime: 24 May 2022 09:13:50.3395 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 46c98d88-e344-4ed4-8496-4ed7712e255d X-MS-Exchange-CrossTenant-mailboxtype: HOSTED X-MS-Exchange-CrossTenant-userprincipalname: InDtmsdlbkkIrsC8yfBj7EyKVtCZ8Uz33N0b/uWAlqIsJG4BqPxHtUji31A/GFFqY0gd0dIjVMiYk+Wv0AS0d5mDstOWyaBdq40MEV4NKfI= X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR11MB4463 X-OriginatorOrg: intel.com X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: users-bounces@dpdk.org --_000_PH0PR11MB5013E6CD6BD9C5F4A6CDD1BB9FD79PH0PR11MB5013namp_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable I should use debug_hexdump(stdout, "encrypted message", asym_op->rsa.cipher.data, asym_op->rsa.cipher.length); to check the encrypted message for the input given? Yes, currently it works this way. The same way output for decryption will b= e placed in asym_op->rsa.message.data and input in asym_op->rsa.cipher.data= . More explanations can be found in rte_crypto_asym.h file https://doc.dpdk.org/api/structrte__crypto__rsa__op__param.html. From: Balakrishnan K Sent: Tuesday, May 24, 2022 7:24 AM To: Kusztal, ArkadiuszX ; users@dpdk.org Subject: RE: how to use crypto openssl PMD for asymmetric encryption and de= cryption Hi Arek, Thanks for quick response. I am using resulted output vector to verify the encrypted message. I thought the encrypted data will be in the asym_op->rsa.message.data after= rte_cryptodev_enqueue_burst and rte_cryptodev_enqueue_burst call with oper= ation type RTE_CRYPTO_ASYM_OP_ENCRYPT. So ,I checked the hex_dump of asym_op->rsa.message.data. Code snippet: asym_op =3D result_op->asym; debug_hexdump(stdout, "encrypted message", asym_op->rsa.message.data, asym_op->rsa.message.length); Encrypted data will be placed in asym_op->rsa.cipher.data after crypto oper= ation is my understanding is correct ? I should use debug_hexdump(stdout, "encrypted message", asym_op->rsa.cipher.data, asym_op->rsa.cipher.length); to check the encrypted message for the input given? Regards, Bala From: Kusztal, ArkadiuszX > Sent: 23 May 2022 18:15 To: Balakrishnan K >; users@dpdk.org Subject: RE: how to use crypto openssl PMD for asymmetric encryption and de= cryption CAUTION: This email originated from outside of the organization. Do not cli= ck links or open attachments unless you recognize the sender and know the c= ontent is safe. Hi Bala, Ciphertext will be written into asym_op->rsa.cipher.data (not message.data)= by the PMD, here you are using same address for both hex dumps. Although there is a bug in debug_hexdump in this function which may cause t= his confusion. Plus, the test you are referring is PWCT test (Pairwise conditional test) -= > it will encrypt, then decrypt. Please take a look into this comment in queue_ops_rsa_enc_dec function: /* Use the resulted output as decryption Input vector* So above this line there is an encryption part. Below is decryption. Regards, Arek From: Balakrishnan K > Sent: Monday, May 23, 2022 1:33 PM To: users@dpdk.org Subject: how to use crypto openssl PMD for asymmetric encryption and decryp= tion Hi All, I am new to dpdk. Planning to use openssl crypto PMD for encrypting/decr= ypting the packets. Couldn't find much documents on openssl PMD for asymmetric encryption/decry= ption. Any one please point me in the right document. I have tried to run the test cases wrote for asymmetric crypto using openss= l virtual PMD. But the output of particular test case is same after the encryption done. File : app/test/test_cryptodev_asym.c Test executable: ./app/test/dpdk-test Test case : test_rsa_enc_dec Input given to encryption: message at [0x1894e60], len=3D20 00000000: F8 BA 1A 55 D0 2F 85 AE 96 7B B6 2F B6 CD A8 EB | ...U./...{./...= . 00000010: 7E 78 A0 50 | ~x.P After processing the output also looks like same : encrypted message exist at [0x1894e60], len=3D20 00000000: F8 BA 1A 55 D0 2F 85 AE 96 7B B6 2F B6 CD A8 EB | ...U./...{./...= . 00000010: 7E 78 A0 50 Regards, Bala --_000_PH0PR11MB5013E6CD6BD9C5F4A6CDD1BB9FD79PH0PR11MB5013namp_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable 
I should use 
debug_hexdump(stdout, "encrypted message", asym_op->rsa.c=
ipher.data,
           &nbs=
p;          asym_op->rsa.ci=
pher.length);
to check the encrypted message for the input given?

 

Yes, currently it works this way. The same way outpu= t for decryption will be placed in asym_op->rsa.message.data and input i= n asym_op->rsa.cipher.data.

More explanations can be found in rte_crypto_asym.h = file

https://doc.dpdk.org/api/structrte__crypto__rsa__op= __param.html.

 

From: Balakrishnan K <Balakrishnan.K1@tata= communications.com>
Sent: Tuesday, May 24, 2022 7:24 AM
To: Kusztal, ArkadiuszX <arkadiuszx.kusztal@intel.com>; users@= dpdk.org
Subject: RE: how to use crypto openssl PMD for asymmetric encryption= and decryption

 

Hi Arek,

   Thanks for quick response.

I am using resulted output vector to verify the encr= ypted message.

I thought the encrypted data will be in the asym_op->rsa.message.d=
ata after rte_cryptodev_enqueue_burst and rte_cryptodev_enqueue_burst call =
with operation type RTE_CRYPTO_ASYM_OP_ENCRYPT.
So ,I checked the hex_dump of asym_op->rsa.message.data.
 
Code snippet:
asym_op =3D result_op->asym;
debug_hexdump(stdout, "encrypted message", asym_op->rsa.m=
essage.data,
           &nbs=
p;          asym_op->rsa.me=
ssage.length);
 
 
 
Encrypted data will be placed in asym_op->rsa.cipher.=
data after crypto operation is my understanding is correct ?

I should use 


debug_hexdump(stdout, "encrypted message", asym_op->rsa.c=
ipher.data,


           &nbs=
p;          asym_op->rsa.ci=
pher.length);


to check the encrypted message for the input given?


 


 


Regards,


Bala 


 


 






From: Kusztal, ArkadiuszX <arkadiuszx.kusztal@intel.com>


Sent: 23 May 2022 18:15

To: Balakrishnan K <Balakrishnan.K1@tatacommunications.com>;
users@dpdk.org

Subject: RE: how to use crypto openssl PMD for asymmetric encryption=
 and decryption






 




CAUTION: This email =
originated from outside of the organization. Do not click links or open att=
achments unless you recognize the sender
 and know the content is safe. 






Hi Bala,


 


Ciphertext will be written into asym_op->rsa.ciph=
er.data (not message.data) by the PMD, here you are using same address for =
both hex dumps.


Although there is a bug in debug_hexdump in this fun=
ction which may cause this confusion.


 


Plus, the test you are referring is PWCT test (Pairw=
ise conditional test) -> it will encrypt, then decrypt.


Please take a look into this comment in queue_ops_rs=
a_enc_dec function:


/* Use the resulted output as decryption Input vecto=
r*


So above this line there is an encryption part.=



Below is decryption.     &n=
bsp;     


 


Regards,


Arek


 








From: Balakrishnan K <Balakrishnan.K1@tatacommunications.com>


Sent: Monday, May 23, 2022 1:33 PM

To: users@dpdk.org

Subject: how to use crypto openssl PMD for asymmetric encryption and=
 decryption






 


Hi All,


   I am new to dpdk. Planning to use opens=
sl crypto PMD for encrypting/decrypting  the packets.


Couldn’t find much documents on openssl PMD fo=
r asymmetric encryption/decryption.


Any one please point me in the right document.<=
/o:p>


 


I have tried to run the test cases wrote for asymmet=
ric crypto using openssl virtual PMD.


But the output of particular test case is same after=
 the encryption done.


 


File : app/test/test_cryptodev_asym.c


Test executable: ./app/test/dpdk-test


Test case : test_rsa_enc_dec


    


Input given to encryption:    =
;          


message at [0x1894e60], len=3D20


00000000: F8 BA 1A 55 D0 2F 85 AE 96 7B B6 2F B6 CD =
A8 EB | ...U./...{./....


00000010: 7E 78 A0 50     &=
nbsp;           &nbs=
p;            &=
nbsp;      | ~x.P


 


After processing the output also looks like same =
:


encrypted message exist at [0x1894e60], len=3D20


00000000: F8 BA 1A 55 D0 2F 85 AE 96 7B B6 2F B6 CD =
A8 EB | ...U./...{./....


00000010: 7E 78 A0 50


 


 


Regards,


Bala
--_000_PH0PR11MB5013E6CD6BD9C5F4A6CDD1BB9FD79PH0PR11MB5013namp_--