From: Akhil Goyal <akhil.goyal@nxp.com>
To: "Trahe, Fiona" <fiona.trahe@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "Kusztal, ArkadiuszX" <arkadiuszx.kusztal@intel.com>,
"Dybkowski, AdamX" <adamx.dybkowski@intel.com>
Subject: Re: [dpdk-dev] [PATCH] cryptodev: clarify wireless inputs in digest-encrypted cases
Date: Tue, 22 Oct 2019 12:08:21 +0000 [thread overview]
Message-ID: <VE1PR04MB6639E1C75A1F06DBAA0E2BF4E6680@VE1PR04MB6639.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <348A99DA5F5B7549AA880327E580B435A217B6E0@IRSMSX101.ger.corp.intel.com>
>
> Hi Akhil,
>
> >
> > Hi Fiona,
> >
> > >
> > > Clarify constraints on fields specified in bits for wireless
> > > algorithms in digest-encrypted case.
> > >
> > > Signed-off-by: Fiona Trahe <fiona.trahe@intel.com>
> > > ---
> > > lib/librte_cryptodev/rte_crypto_sym.h | 7 +++++++
> > > 1 files changed, 7 insertions(+), 0 deletions(-)
> > >
> > > diff --git a/lib/librte_cryptodev/rte_crypto_sym.h
> > > b/lib/librte_cryptodev/rte_crypto_sym.h
> > > index bc8da24..0204d37 100644
> > > --- a/lib/librte_cryptodev/rte_crypto_sym.h
> > > +++ b/lib/librte_cryptodev/rte_crypto_sym.h
> > > @@ -703,6 +703,13 @@ struct rte_crypto_sym_op {
> > > * auth.data.length and is typically
> > > * equal to auth.data.offset +
> > > * auth.data.length + digest_length.
> > > + * - for wireless algorithms, i.e.
> > > + * SNOW 3G, KASUMI and ZUC, as the
> > > + * cipher.data.length,
> > > + * cipher.data.offset,
> > > + * auth.data.length and
> > > + * auth.data.offset are in bits, they
> > > + * must be 8-bit multiples.
> >
> > What is the meaning of 'they' here?
> > cipher.data.length, cipher.data.offset, auth.data.length and auth.data.offset
> are in bits
> > and may or may not be multiple of 8bits. This is documented in their comments.
> >
> [Fiona] This added note is an extra bullet under the explanation for Digest-
> encrypted cases.
> In these cases only those fields listed MUST be 8-bit multiples.
> Can you suggest a change that would make that clearer?
@@ -590,7 +590,9 @@ struct rte_crypto_sym_op {
* For SNOW 3G @ RTE_CRYPTO_CIPHER_SNOW3G_UEA2,
* KASUMI @ RTE_CRYPTO_CIPHER_KASUMI_F8
* and ZUC @ RTE_CRYPTO_CIPHER_ZUC_EEA3,
- * this field should be in bits.
+ * this field should be in bits and must be
+ * 8-bit multiples in cases of encrypted
+ * digest.
*/
Same change may be done in other 3 fields.
>
>
> >
> > > *
> > > * Note, that for security reasons, it
> > > * is PMDs' responsibility to not
> > > --
> > > 1.7.0.7
next prev parent reply other threads:[~2019-10-22 12:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-22 11:34 Fiona Trahe
2019-10-22 11:48 ` Akhil Goyal
2019-10-22 12:00 ` Trahe, Fiona
2019-10-22 12:08 ` Akhil Goyal [this message]
2019-10-22 12:32 ` Trahe, Fiona
2019-10-22 13:20 ` [dpdk-dev] [PATCH v2] " Fiona Trahe
2019-10-22 13:24 ` Akhil Goyal
2019-10-22 14:46 ` Trahe, Fiona
2019-10-23 14:59 ` 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=VE1PR04MB6639E1C75A1F06DBAA0E2BF4E6680@VE1PR04MB6639.eurprd04.prod.outlook.com \
--to=akhil.goyal@nxp.com \
--cc=adamx.dybkowski@intel.com \
--cc=arkadiuszx.kusztal@intel.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).