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 42C1CA0548; Tue, 31 May 2022 07:13:03 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id D308242B74; Tue, 31 May 2022 07:12:44 +0200 (CEST) Received: from mga07.intel.com (mga07.intel.com [134.134.136.100]) by mails.dpdk.org (Postfix) with ESMTP id B1C9442B70 for ; Tue, 31 May 2022 07:12:42 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1653973962; x=1685509962; h=from:to:cc:subject:date:message-id:in-reply-to: references; bh=NzBDSr+/emIoxe7kzNHipunAk6OPlawnam5sHU5OkI4=; b=D6lxkFOHhT6kHy+gxmKXZ3OeH0w7qsOEzwxRooXksFhISLu51eK/8baW fP4vaPHypt57RS26nnI1s+0lOPCy2JbBPwNEEFLNagu0kUQEPYvXNUtcz gyP3c6rAq9gF4wfdCEi6PHTkDfzDB0igdVMjly5AcDa2mLujoEH4ItTMu VXmhI0wcLWIxyUIh091ktIrucx63sYPPZv04cBE0ojdbDbEuXw48r0SYt mp3IHioJ82y3rKX/o/jWEY0fYoPHKcspqgXBS3W1q+xmkoJXH2zFGFvyx L5tSi8jMmVpxuV8TGmgwbQXhH6lpM5i6g5Pli0rD3VyDS0YUXd+/x6yEB A==; X-IronPort-AV: E=McAfee;i="6400,9594,10363"; a="338181293" X-IronPort-AV: E=Sophos;i="5.91,264,1647327600"; d="scan'208";a="338181293" Received: from orsmga007.jf.intel.com ([10.7.209.58]) by orsmga105.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 30 May 2022 22:12:42 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.91,264,1647327600"; d="scan'208";a="576220433" Received: from silpixa00399302.ir.intel.com ([10.237.214.136]) by orsmga007.jf.intel.com with ESMTP; 30 May 2022 22:12:41 -0700 From: Arek Kusztal To: dev@dpdk.org Cc: gakhil@marvell.com, roy.fan.zhang@intel.com, Arek Kusztal Subject: [PATCH v4 04/12] cryptodev: clarify usage of private key in dh Date: Tue, 31 May 2022 05:04:31 +0100 Message-Id: <20220531040439.15862-5-arkadiuszx.kusztal@intel.com> X-Mailer: git-send-email 2.13.6 In-Reply-To: <20220531040439.15862-1-arkadiuszx.kusztal@intel.com> References: <20220531040439.15862-1-arkadiuszx.kusztal@intel.com> X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org - Clarified usage of private key in Diffie-Hellman. CSRNG capable device should generate private key and then use it for public key generation. Signed-off-by: Arek Kusztal --- lib/cryptodev/rte_crypto_asym.h | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/lib/cryptodev/rte_crypto_asym.h b/lib/cryptodev/rte_crypto_asym.h index eb753b4016..619c0614bf 100644 --- a/lib/cryptodev/rte_crypto_asym.h +++ b/lib/cryptodev/rte_crypto_asym.h @@ -416,6 +416,11 @@ struct rte_crypto_dh_op_param { * Input - private key, when dh xform ke_type is one of: * RTE_CRYPTO_ASYM_KE_PUB_KEY_GENERATE, * RTE_CRYPTO_ASYM_KE_SHARED_SECRET_COMPUTE. + * + * In case priv_key.length is 0 and xform type is set with + * RTE_CRYPTO_ASYM_KE_PUB_KEY_GENERATE, CSRNG capable + * device will generate a private key and use it for public + * key generation. */ rte_crypto_uint shared_secret; -- 2.13.6