From: Naveen Kumar <Naveen.Kumar@commagility.com> To: "Trahe, Fiona" <firstname.lastname@example.org>, "email@example.com" <firstname.lastname@example.org> Subject: Re: [dpdk-users] AES "Digest-encrypted" crypto chain case. Date: Mon, 9 Sep 2019 14:27:43 +0000 Message-ID: <email@example.com> (raw) In-Reply-To: <348A99DA5F5B7549AA880327E580B4358981225E@IRSMSX101.ger.corp.intel.com> Hi Fiona, Thanks for prompt response. I observe digest overwriting issue with below combination (chained): // auth_xform->type = RTE_CRYPTO_SYM_XFORM_AUTH; auth_xform->auth.algo = RTE_CRYPTO_AUTH_AES_CMAC; auth_xform->auth.op = RTE_CRYPTO_AUTH_OP_GENERATE; cipher_xform->type = RTE_CRYPTO_SYM_XFORM_CIPHER; cipher_xform->cipher.algo = RTE_CRYPTO_CIPHER_AES_CTR; cipher_xform->cipher.op = RTE_CRYPTO_CIPHER_OP_ENCRYPT; // Testing with snow3g and ZUC on same test suite i.e, encryption including digest, works as expected. 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. -----Original Message----- From: Trahe, Fiona <firstname.lastname@example.org> Sent: Monday, September 9, 2019 4:09 PM To: Naveen Kumar <Naveen.Kumar@commagility.com>; email@example.com Cc: Trahe, Fiona <firstname.lastname@example.org> Subject: RE: [dpdk-users] AES "Digest-encrypted" crypto chain case. 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:email@example.com] On Behalf Of Naveen Kumar > Sent: Monday, September 9, 2019 10:16 AM > To: firstname.lastname@example.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 index 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 2019-09-09 14:27 ` Naveen Kumar [this message] 2019-10-16 12:48 Dybkowski, AdamX [not found] ` <email@example.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 publically 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 \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.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
DPDK usage discussions Archives are clonable: git clone --mirror http://inbox.dpdk.org/users/0 users/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 users users/ http://inbox.dpdk.org/users \ firstname.lastname@example.org public-inbox-index users Newsgroup available over NNTP: nntp://inbox.dpdk.org/inbox.dpdk.users AGPL code for this site: git clone https://public-inbox.org/ public-inbox