From: "Kusztal, ArkadiuszX" <arkadiuszx.kusztal@intel.com>
To: Akhil Goyal <gakhil@marvell.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "Zhang, Roy Fan" <roy.fan.zhang@intel.com>
Subject: RE: [EXT] [PATCH v2 03/14] cryptodev: separate key exchange operation enum
Date: Thu, 26 May 2022 11:06:24 +0000 [thread overview]
Message-ID: <PH0PR11MB5013A8C56DD2E13D8201B8FA9FD99@PH0PR11MB5013.namprd11.prod.outlook.com> (raw)
In-Reply-To: <CO6PR18MB4484BDF45BE25B5FEE42CB39D8D99@CO6PR18MB4484.namprd18.prod.outlook.com>
> -----Original Message-----
> From: Akhil Goyal <gakhil@marvell.com>
> Sent: Thursday, May 26, 2022 12:58 PM
> To: Kusztal, ArkadiuszX <arkadiuszx.kusztal@intel.com>; dev@dpdk.org
> Cc: Zhang, Roy Fan <roy.fan.zhang@intel.com>
> Subject: RE: [EXT] [PATCH v2 03/14] cryptodev: separate key exchange
> operation enum
>
> > /**
> > + * Asymmetric crypto key exchange operation type */ enum
> > +rte_crypto_asym_ke_type {
> > + RTE_CRYPTO_ASYM_KE_PRIVATE_KEY_GENERATE,
>
> Is it better to shorten it to
> RTE_CRYPTO_ASYM_KE_PRIV_KEY_GENERATE
> RTE_CRYPTO_ASYM_KE_PUB_KEY_GENERATE
+1, Actually I am not big fan of having asym everywhere too.
RTE_CRYPTO_KE_PRIV_KEY_GENERATE would be equally good.
>
> > + /**< Private Key generation operation */
> > + RTE_CRYPTO_ASYM_KE_PUBLIC_KEY_GENERATE,
> > + /**< Public Key generation operation */
> > + RTE_CRYPTO_ASYM_KE_SHARED_SECRET_COMPUTE
> > + /**< Shared Secret compute operation */ };
> > +
> > +/**
> > * Padding types for RSA signature.
> > */
> > enum rte_crypto_rsa_padding_type {
> > @@ -238,7 +248,7 @@ struct rte_crypto_modinv_xform {
> > *
> > */
> > struct rte_crypto_dh_xform {
> > - enum rte_crypto_asym_op_type type;
> > + enum rte_crypto_asym_ke_type type;
> > /**< Setup xform for key generate or shared secret compute */
> > rte_crypto_uint p;
> > /**< Prime modulus data */
> > @@ -375,26 +385,27 @@ struct rte_crypto_rsa_op_param { struct
> > rte_crypto_dh_op_param {
> > rte_crypto_uint pub_key;
> > /**<
> > - * Output generated public key when xform type is
> > - * DH PUB_KEY_GENERATION.
> > - * Input peer public key when xform type is DH
> > - * SHARED_SECRET_COMPUTATION
> > + * Output - generated public key, when xform type is
>
> It is not xform type, Right?
> It should be key exchange type.
Yes, I meant xform op_type. Will change, leter it will be overwritten by move dh op patch too.
> Check at other places also.
>
> > + * RTE_CRYPTO_ASYM_KE_PUBLIC_KEY_GENERATE.
> > *
> > + * Input - peer's public key, when xform type is
> > + * RTE_CRYPTO_ASYM_KE_SHARED_SECRET_COMPUTE.
> > */
> >
> > rte_crypto_uint priv_key;
> > /**<
> > - * Output generated private key if xform type is
> > - * DH PRIVATE_KEY_GENERATION
> > - * Input when xform type is DH SHARED_SECRET_COMPUTATION.
> > + * Output - generated private key, when xform type is
> > + * RTE_CRYPTO_ASYM_KE_PRIVATE_KEY_GENERATE.
> > *
> > + * Input - private key, when xform type is one of:
> > + * RTE_CRYPTO_ASYM_KE_PUBLIC_KEY_GENERATE,
> > + * RTE_CRYPTO_ASYM_KE_SHARED_SECRET_COMPUTE.
> > */
> >
> > rte_crypto_uint shared_secret;
> > /**<
> > - * Output with calculated shared secret
> > - * when dh xform set up with op type =
> > SHARED_SECRET_COMPUTATION.
> > - *
> > + * Output - calculated shared secret when xform type is
> > + * RTE_CRYPTO_ASYM_KE_SHARED_SECRET_COMPUTE.
> > */
> > };
> >
next prev parent reply other threads:[~2022-05-26 11:06 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-25 15:53 [PATCH v2 00/14] cryptodev: rsa, dh, ecdh changes Arek Kusztal
2022-05-25 15:53 ` [PATCH v2 01/14] cryptodev: redefine ec group enum Arek Kusztal
2022-05-26 9:40 ` [EXT] " Akhil Goyal
2022-05-25 15:53 ` [PATCH v2 02/14] cryptodev: reduce number of comments in asym xform Arek Kusztal
2022-05-26 9:52 ` [EXT] " Akhil Goyal
2022-05-26 10:03 ` Kusztal, ArkadiuszX
2022-05-25 15:53 ` [PATCH v2 03/14] cryptodev: separate key exchange operation enum Arek Kusztal
2022-05-26 10:57 ` [EXT] " Akhil Goyal
2022-05-26 11:06 ` Kusztal, ArkadiuszX [this message]
2022-05-26 11:09 ` Akhil Goyal
2022-05-25 15:53 ` [PATCH v2 04/14] cryptodev: remove comment about using ephemeral key in dsa Arek Kusztal
2022-05-26 11:02 ` [EXT] " Akhil Goyal
2022-05-25 15:53 ` [PATCH v2 05/14] cryptodev: clarify usage of private key in dh Arek Kusztal
2022-05-26 11:04 ` [EXT] " Akhil Goyal
2022-05-25 15:53 ` [PATCH v2 06/14] cryptodev: move dh type from xform to dh op Arek Kusztal
2022-05-26 11:23 ` [EXT] " Akhil Goyal
2022-05-25 15:53 ` [PATCH v2 07/14] cryptodev: add elliptic curve diffie hellman Arek Kusztal
2022-05-26 11:29 ` [EXT] " Akhil Goyal
2022-05-26 11:44 ` Kusztal, ArkadiuszX
2022-05-25 15:53 ` [PATCH v2 08/14] cryptodev: add public key verify option Arek Kusztal
2022-05-26 11:34 ` [EXT] " Akhil Goyal
2022-05-26 11:46 ` Kusztal, ArkadiuszX
2022-05-25 15:53 ` [PATCH v2 09/14] cryptodev: add asym op flags Arek Kusztal
2022-05-26 11:46 ` [EXT] " Akhil Goyal
2022-05-25 15:53 ` [PATCH v2 10/14] cryptodev: clarify usage of rsa padding hash Arek Kusztal
2022-05-26 11:56 ` [EXT] " Akhil Goyal
2022-05-25 15:53 ` [PATCH v2 11/14] cryptodev: move RSA padding into separate struct Arek Kusztal
2022-05-26 12:04 ` [EXT] " Akhil Goyal
2022-05-26 12:14 ` Kusztal, ArkadiuszX
2022-05-26 12:19 ` Akhil Goyal
2022-05-26 12:35 ` Kusztal, ArkadiuszX
2022-05-26 12:41 ` Akhil Goyal
2022-05-25 15:53 ` [PATCH v2 12/14] cryptodev: clarify rsa verify with none padding Arek Kusztal
2022-05-26 12:06 ` [EXT] " Akhil Goyal
2022-05-26 12:15 ` Kusztal, ArkadiuszX
2022-05-25 15:53 ` [PATCH v2 13/14] cryptodev: add salt length and optional label Arek Kusztal
2022-05-26 12:08 ` [EXT] " Akhil Goyal
2022-05-25 15:53 ` [PATCH v2 14/14] cryptodev: add asym algorithms capabilities Arek Kusztal
2022-05-26 12:54 ` [EXT] " Akhil Goyal
2022-05-26 14:19 ` Kusztal, ArkadiuszX
2022-05-26 15:00 ` 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=PH0PR11MB5013A8C56DD2E13D8201B8FA9FD99@PH0PR11MB5013.namprd11.prod.outlook.com \
--to=arkadiuszx.kusztal@intel.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--cc=roy.fan.zhang@intel.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).