From: "Trahe, Fiona" <fiona.trahe@intel.com>
To: Naveen Kumar <Naveen.Kumar@commagility.com>,
"users@dpdk.org" <users@dpdk.org>
Cc: "Trahe, Fiona" <fiona.trahe@intel.com>
Subject: Re: [dpdk-users] AES "Digest-encrypted" crypto chain case.
Date: Mon, 9 Sep 2019 14:08:52 +0000 [thread overview]
Message-ID: <348A99DA5F5B7549AA880327E580B4358981225E@IRSMSX101.ger.corp.intel.com> (raw)
In-Reply-To: <8bbd488f54dc428ab9ec046639a633d0@de-mta1.commagility.com>
Hi Naveen,
Which chain exactly are you testing? i.e. which cipher mode, which auth algorithm?
Our tests so far have focussed on ZUC and Snow3G use-cases.
Fiona
> -----Original Message-----
> From: users [mailto:users-bounces@dpdk.org] On Behalf Of Naveen Kumar
> Sent: Monday, September 9, 2019 10:16 AM
> To: users@dpdk.org
> Subject: [dpdk-users] AES "Digest-encrypted" crypto chain case.
>
> Hi All,
> I am trying to test AES symmetric crypto case "Digest-encrypted" by chaining Authentication operation
> followed by Ciphering.
> Digest data pointer, Ciphering lengths etc., are configured such that ciphering operation includes the
> digest data (as mentioned in ‘rte_crypto_sym.h’ line:650-715).
>
> With QAT PMD, I see the ‘raw’ digest data overwritten on the ciphered output as end result.
>
> This issue is seen only with AES - ‘Digest-Encrypt’ chained operation. Not with Snow3G/ZUC chained
> operations.
>
> Does anyone face this issue?
>
> Regards,
> Naveen
>
> --
> Naveen Kumar
> Senior Engineer
>
> CommAgility is a Wireless Telecom Group company
> T: +49 (0)203 306 4537 | www.commagility.com
> Registered in England, Company No. 05914025. VAT No. DE299686390
> CommAgility is an ISO 9001:2015-certified company
> This email is confidential, for recipient’s use only.
next prev parent reply other threads:[~2019-09-09 14:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-09 9:15 Naveen Kumar
2019-09-09 14:08 ` Trahe, Fiona [this message]
2019-09-09 14:27 ` Naveen Kumar
2019-10-16 12:48 Dybkowski, AdamX
[not found] ` <9836169a72be40328d96c3c08e78ad3d@de-mta1.commagility.com>
2019-10-17 15:30 ` Naveen Kumar
2019-10-18 13:19 ` Dybkowski, AdamX
2019-11-05 11:17 ` Naveen Kumar
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=348A99DA5F5B7549AA880327E580B4358981225E@IRSMSX101.ger.corp.intel.com \
--to=fiona.trahe@intel.com \
--cc=Naveen.Kumar@commagility.com \
--cc=users@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
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).