[EXT] [PATCH v2 05/14] cryptodev: clarify usage of private key in dh

Akhil Goyal gakhil at marvell.com
Thu May 26 13:04:29 CEST 2022


> - 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 <arkadiuszx.kusztal at intel.com>
> ---
>  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 ef8686fda8..1a77a74478 100644
> --- a/lib/cryptodev/rte_crypto_asym.h
> +++ b/lib/cryptodev/rte_crypto_asym.h
> @@ -394,6 +394,11 @@ struct rte_crypto_dh_op_param {
>  	 * Input - private key, when xform type is one of:
>  	 * RTE_CRYPTO_ASYM_KE_PUBLIC_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_PUBLIC_KEY_GENERATE, CSRNG capable
> +	 * device will generate private key and use it for public
> +	 * key generation.
>  	 */
Capability for CSRNG?

Acked-by: Akhil Goyal <gakhil at marvell.com>


More information about the dev mailing list