DPDK patches and discussions
 help / color / mirror / Atom feed
From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: Akhil Goyal <akhil.goyal@nxp.com>,
	"Verma, Shally" <Shally.Verma@cavium.com>
Cc: "Trahe, Fiona" <fiona.trahe@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>,
	"Athreya, Narayana Prasad" <NarayanaPrasad.Athreya@cavium.com>,
	"Sahu, Sunila" <Sunila.Sahu@cavium.com>,
	"Gupta, Ashish" <Ashish.Gupta@cavium.com>
Subject: Re: [dpdk-dev] [PATCH v3 4/6] test/crypto: add unit testcase for asym crypto
Date: Mon, 18 Jun 2018 08:38:42 +0000	[thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D8977F8D7082@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <7beb0f7b-7179-c3a1-5e50-f51db1c76ff3@nxp.com>

Hi,

> -----Original Message-----
> From: Akhil Goyal [mailto:akhil.goyal@nxp.com]
> Sent: Monday, June 18, 2018 8:35 AM
> To: Verma, Shally <Shally.Verma@cavium.com>; Akhil Goyal
> <akhil.goyal@nxp.com>; De Lara Guarch, Pablo
> <pablo.de.lara.guarch@intel.com>
> Cc: Trahe, Fiona <fiona.trahe@intel.com>; dev@dpdk.org; Athreya, Narayana
> Prasad <NarayanaPrasad.Athreya@cavium.com>; Sahu, Sunila
> <Sunila.Sahu@cavium.com>; Gupta, Ashish <Ashish.Gupta@cavium.com>
> Subject: Re: [dpdk-dev] [PATCH v3 4/6] test/crypto: add unit testcase for asym
> crypto
> 
> Hi Shally,
> On 6/18/2018 12:18 PM, Verma, Shally wrote:
> > Hi
> >
> >> -----Original Message-----
> >> From: Akhil Goyal [mailto:akhil.goyal@nxp.com]
> >> Sent: 18 June 2018 12:10
> >> To: Verma, Shally <Shally.Verma@cavium.com>; De Lara Guarch, Pablo
> >> <pablo.de.lara.guarch@intel.com>
> >> Cc: Trahe, Fiona <fiona.trahe@intel.com>; akhil.goyal@nxp.com;
> >> dev@dpdk.org; Athreya, Narayana Prasad
> >> <NarayanaPrasad.Athreya@cavium.com>; Sahu, Sunila
> >> <Sunila.Sahu@cavium.com>; Gupta, Ashish <Ashish.Gupta@cavium.com>
> >> Subject: Re: [dpdk-dev] [PATCH v3 4/6] test/crypto: add unit testcase
> >> for asym crypto
> >>
> >
> > //snip
> >
> >>>>>>> +static int
> >>>>>>> +test_rsa(struct rsa_test_data *t)
> >>>>>>
> >>>>>> ...
> >>>>>>
> >>>>>>> +     rsa->n =
> >>>>>>> +             BN_bin2bn(
> >>>>>>> +                     (const unsigned char *)rsa_xform.rsa.n.data,
> >>>>>>> +                     rsa_xform.rsa.n.length,
> >>>>>>> +                     rsa->n);
> >>>>>>
> >>>>>> I am getting a compilation error:
> >>>>>>
> >>>>>> /test/test/test_cryptodev_asym.c:322:5: error:
> >>>>>> dereferencing pointer to incomplete type 'RSA {aka struct rsa_st}'
> >>>>>>  rsa->n =
> >>>>>>     ^~
> >>>>>>
> >>>>>> My OpenSSL version is 1.1.0h.
> >>>>>>
> >>>>> [Shally] This library is tested with version 1.0.2m (mentioned
> >>>>> above) and also one supported by openssl PMD . So, you need to take
> similar version.
> >>>>
> >>>> I'd say we should support the latest stable version of OpenSSL.
> >>>> Could you get the latest 1.1.0?
> >>> [Shally] Openssl PMD uses 1.0.2h. If we move test to 1.1.0 then dpdk
> >>> would need to be set to link to two different version of libcrypto whenever
> openssl PMD is enabled which seems like a cumbersome process for users.
> >>> So I recommend for now to stick to one version.
> >>>
> >>
> >> OpenSSL PMD can get compiled/linked with any of the versions 1.0.2 or
> >> 1.1. We cannot control the above applications which version it is using.
> >> So we should not add limitation for openssl version. Please check
> >> below snippet in the PMD if this is suitable in your case.
> >>
> >> +#if (OPENSSL_VERSION_NUMBER < 0x10100000L) static HMAC_CTX
> >> +*HMAC_CTX_new(void) {
> >> +       HMAC_CTX *ctx = OPENSSL_malloc(sizeof(*ctx));
> >> +
> >> +       if (ctx != NULL)
> >> +               HMAC_CTX_init(ctx);
> >> +       return ctx;
> >> +}
> >> +
> >> +static void HMAC_CTX_free(HMAC_CTX *ctx) {
> >> +       if (ctx != NULL) {
> >> +               HMAC_CTX_cleanup(ctx);
> >> +               OPENSSL_free(ctx);
> >> +       }
> >> +}
> >> +#endif
> >>
> > [Shally] Are we just planning to make PMD/test compatible for all lib versions?
> Won't it then be too many version compatibility checks in PMD/test and a
> maintainability issue than having implementation mentioned to be compatible
> with specific version?
> >
> 
> I think we should at least support the latest stable version. As per the openssl
> website "The latest stable version is the 1.1.0 series. The
> 1.0.2 series is our Long Term Support (LTS) release, supported until 31st
> December 2019". I think Pablo also suggested to support openssl 1.1.

I think we should keep supporting OpenSSL 1.1, even though our documentation
says that we support up to 1.0.2 (which we should fix!).
Knowing that Ubuntu and Fedora have 1.1 version in their latest versions,
I think it is a good idea to keep supporting this,
As many users will be using this version and we would be breaking their code if he change this.

Thanks,
Pablo

> 
> Thanks,
> Akhil
> >>
> >>> Thanks
> >>> Shally
> >>>
> >>>>
> >>>> Thanks,
> >>>> Pablo
> >

  reply	other threads:[~2018-06-18  8:38 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-16  6:05 [dpdk-dev] [PATCH v3 0/6] crypto: add asym crypto support Shally Verma
2018-05-16  6:05 ` [dpdk-dev] [PATCH v3 1/6] lib/cryptodev: add asymmetric algos in cryptodev Shally Verma
2018-06-15  8:40   ` De Lara Guarch, Pablo
2018-06-22 15:38     ` Verma, Shally
2018-06-25 21:34       ` De Lara Guarch, Pablo
2018-06-26 11:54         ` Verma, Shally
2018-05-16  6:05 ` [dpdk-dev] [PATCH v3 2/6] lib/cryptodev: add asym op support " Shally Verma
2018-06-15  9:05   ` De Lara Guarch, Pablo
2018-06-26  9:20   ` De Lara Guarch, Pablo
2018-06-26 11:21     ` Verma, Shally
2018-05-16  6:05 ` [dpdk-dev] [PATCH v3 3/6] lib/cryptodev: add asymmetric crypto capability " Shally Verma
2018-06-17 12:11   ` De Lara Guarch, Pablo
2018-07-03 14:12   ` Trahe, Fiona
2018-07-03 14:47     ` Verma, Shally
2018-05-16  6:05 ` [dpdk-dev] [PATCH v3 4/6] test/crypto: add unit testcase for asym crypto Shally Verma
2018-06-17 12:52   ` De Lara Guarch, Pablo
2018-06-17 15:01     ` Verma, Shally
2018-06-17 19:31       ` De Lara Guarch, Pablo
2018-06-18  5:40         ` Verma, Shally
2018-06-18  6:39           ` Akhil Goyal
2018-06-18  6:48             ` Verma, Shally
2018-06-18  7:34               ` Akhil Goyal
2018-06-18  8:38                 ` De Lara Guarch, Pablo [this message]
2018-06-18 16:22                   ` Verma, Shally
2018-05-16  6:05 ` [dpdk-dev] [PATCH v3 5/6] crypto/openssl: add asym crypto support Shally Verma
2018-06-17 13:25   ` De Lara Guarch, Pablo
2018-06-17 15:48     ` Verma, Shally
2018-06-17 19:38       ` De Lara Guarch, Pablo
2018-06-18  5:30         ` Verma, Shally
2018-06-23 12:41           ` Verma, Shally
2018-06-23 18:16             ` De Lara Guarch, Pablo
2018-06-23 18:26               ` Verma, Shally
2018-06-25 16:35                 ` De Lara Guarch, Pablo
2018-06-26  9:23   ` De Lara Guarch, Pablo
2018-06-26 11:22     ` Verma, Shally
2018-07-03 14:50   ` Trahe, Fiona
2018-07-03 14:59     ` Verma, Shally
2018-07-03 15:11       ` Trahe, Fiona
2018-07-03 15:14         ` Verma, Shally
2018-05-16  6:05 ` [dpdk-dev] [PATCH v3 6/6] doc: add asym crypto in cryptodev programmer guide Shally Verma
2018-06-14 10:43   ` Kovacevic, Marko
2018-06-15  8:06     ` Verma, Shally
2018-06-17 13:33   ` De Lara Guarch, Pablo
2018-06-17 16:59     ` Verma, Shally

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=E115CCD9D858EF4F90C690B0DCB4D8977F8D7082@IRSMSX108.ger.corp.intel.com \
    --to=pablo.de.lara.guarch@intel.com \
    --cc=Ashish.Gupta@cavium.com \
    --cc=NarayanaPrasad.Athreya@cavium.com \
    --cc=Shally.Verma@cavium.com \
    --cc=Sunila.Sahu@cavium.com \
    --cc=akhil.goyal@nxp.com \
    --cc=dev@dpdk.org \
    --cc=fiona.trahe@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).