From: "Dooley, Brian" <brian.dooley@intel.com>
To: Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: Anoob Joseph <anoobj@marvell.com>, Akhil Goyal <gakhil@marvell.com>
Subject: RE: [PATCH v1] examples/fips_validation: fix EdDSA signature size
Date: Wed, 30 Oct 2024 11:29:03 +0000 [thread overview]
Message-ID: <SJ0PR11MB5056A84A426AD61D6BF335CD83542@SJ0PR11MB5056.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20241029055908.1073-1-gmuthukrishn@marvell.com>
> -----Original Message-----
> From: Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>
> Sent: Tuesday 29 October 2024 05:59
> To: dev@dpdk.org; Dooley, Brian <brian.dooley@intel.com>; Gowrishankar
> Muthukrishnan <gmuthukrishn@marvell.com>
> Cc: Anoob Joseph <anoobj@marvell.com>; Akhil Goyal <gakhil@marvell.com>
> Subject: [PATCH v1] examples/fips_validation: fix EdDSA signature size
>
> Fix EdDSA signature size.
>
> Fixes: 12ede9ac497f ("examples/fips_validation: support EdDSA")
>
> Signed-off-by: Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>
> ---
> examples/fips_validation/fips_validation_eddsa.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/examples/fips_validation/fips_validation_eddsa.c
> b/examples/fips_validation/fips_validation_eddsa.c
> index db118748b6..89fa6c17ca 100644
> --- a/examples/fips_validation/fips_validation_eddsa.c
> +++ b/examples/fips_validation/fips_validation_eddsa.c
> @@ -48,8 +48,8 @@ struct {
> uint8_t curve_len;
> const char *desc;
> } eddsa_curve_len[] = {
> - {32, "ED-25519"},
> - {64, "ED-448"},
> + {64, "ED-25519"},
> + {114, "ED-448"},
> };
>
> #ifdef USE_OPENSSL
> --
> 2.37.1
Acked-by: Brian Dooley <brian.dooley@intel.com>
prev parent reply other threads:[~2024-10-30 11:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-29 5:59 Gowrishankar Muthukrishnan
2024-10-30 11:29 ` Dooley, Brian [this message]
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=SJ0PR11MB5056A84A426AD61D6BF335CD83542@SJ0PR11MB5056.namprd11.prod.outlook.com \
--to=brian.dooley@intel.com \
--cc=anoobj@marvell.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--cc=gmuthukrishn@marvell.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).