patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Archana Muniganti <marchana@marvell.com>
To: Akhil Goyal <akhil.goyal@nxp.com>,
	"marko.kovacevic@intel.com" <marko.kovacevic@intel.com>,
	"roy.fan.zhang@intel.com" <roy.fan.zhang@intel.com>
Cc: Sucharitha Sarananaga <ssarananaga@marvell.com>,
	Anoob Joseph <anoobj@marvell.com>,
	Abed Mohammad Kamaluddin <akamaluddin@marvell.com>,
	Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
	"dev@dpdk.org" <dev@dpdk.org>,
	"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] [PATCH] examples/fips_validation: fix parsing of cipher length for AES-GCM
Date: Mon, 6 Jan 2020 13:44:33 +0000
Message-ID: <MWHPR1801MB2077CAE7C785E2EA82B22EABC33C0@MWHPR1801MB2077.namprd18.prod.outlook.com> (raw)
In-Reply-To: <VE1PR04MB66394A6F5C054E371C15D776E63C0@VE1PR04MB6639.eurprd04.prod.outlook.com>

Hi Akhil,

Please see inline.

Thanks,
Archana

> -----Original Message-----
> From: Akhil Goyal <akhil.goyal@nxp.com>
> Sent: Monday, January 6, 2020 3:09 PM
> To: Archana Muniganti <marchana@marvell.com>;
> marko.kovacevic@intel.com; roy.fan.zhang@intel.com
> Cc: Sucharitha Sarananaga <ssarananaga@marvell.com>; Anoob Joseph
> <anoobj@marvell.com>; Abed Mohammad Kamaluddin
> <akamaluddin@marvell.com>; Jerin Jacob Kollanukkaran
> <jerinj@marvell.com>; dev@dpdk.org; stable@dpdk.org
> Subject: [EXT] RE: [PATCH] examples/fips_validation: fix parsing of cipher
> length for AES-GCM
> 
> External Email
> 
> ----------------------------------------------------------------------
> > From: Sucharitha Sarananaga <ssarananaga@marvell.com>
> >
> > Cipher length need to be updated in case of AES-GCM decryption.
> >
> > Fixes: 4aaad2995e13 ("examples/fips_validation: support GCM parsing")
> >
> > Signed-off-by: Archana Muniganti <marchana@marvell.com>
> > Signed-off-by: Sucharitha Sarananaga <ssarananaga@marvell.com>
> > ---
> >  examples/fips_validation/fips_validation_gcm.c | 2 ++
> >  1 file changed, 2 insertions(+)
> >
> > diff --git a/examples/fips_validation/fips_validation_gcm.c
> > b/examples/fips_validation/fips_validation_gcm.c
> > index ea48ddf..f295025 100644
> > --- a/examples/fips_validation/fips_validation_gcm.c
> > +++ b/examples/fips_validation/fips_validation_gcm.c
> > @@ -19,6 +19,7 @@
> >  #define PTLEN_STR	"PTlen = "
> >  #define AADLEN_STR	"AADlen = "
> >  #define TAGLEN_STR	"Taglen = "
> > +#define CTLEN_STR	"PTlen = "
> Typo. Should be CTlen
[Archana] NIST request file for AES-GCM test vectors contains 'PTlen =' field.
This field holds plain text length when encrypt test vectors are used. And same
field holds cipher text length when decrypt test vectors are used.
Hence added a new macro that will be used in AES-GCM 'decryption'

  reply	other threads:[~2020-01-07 17:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-06  9:33 Archana Muniganti
2020-01-06  9:38 ` Akhil Goyal
2020-01-06 13:44   ` Archana Muniganti [this message]
2020-01-07  7:16 ` Anoob Joseph
2020-02-05 12:29   ` 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=MWHPR1801MB2077CAE7C785E2EA82B22EABC33C0@MWHPR1801MB2077.namprd18.prod.outlook.com \
    --to=marchana@marvell.com \
    --cc=akamaluddin@marvell.com \
    --cc=akhil.goyal@nxp.com \
    --cc=anoobj@marvell.com \
    --cc=dev@dpdk.org \
    --cc=jerinj@marvell.com \
    --cc=marko.kovacevic@intel.com \
    --cc=roy.fan.zhang@intel.com \
    --cc=ssarananaga@marvell.com \
    --cc=stable@dpdk.org \
    /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

patches for DPDK stable branches

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://inbox.dpdk.org/stable/0 stable/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 stable stable/ https://inbox.dpdk.org/stable \
		stable@dpdk.org
	public-inbox-index stable

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.stable


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git