DPDK usage discussions
 help / color / Atom feed
From: "Dybkowski, AdamX" <adamx.dybkowski@intel.com>
To: "users@dpdk.org" <users@dpdk.org>,
	"naveen.kumar@commagility.com" <naveen.kumar@commagility.com>
Cc: "Trahe, Fiona" <fiona.trahe@intel.com>
Subject: Re: [dpdk-users] AES "Digest-encrypted" crypto chain case.
Date: Wed, 16 Oct 2019 12:48:56 +0000
Message-ID: <522B1A062D56224ABC0C6BDBCD64D9D369E6E7F2@IRSMSX103.ger.corp.intel.com> (raw)

Hi Naveen.

Regarding your message sent to dpdk-users mailing list:

We've tested here at Intel the digest-encrypted combination you wrote about, with auth.algo = AES-CMAC and cipher.algo = AES-CTR, and it seems everything works fine.
Do you set the length fields properly when creating the operation? According to the header file rte_crypto_sym.h, in the structure rte_crypto_sym_op, the field cipher.data.length should be written in bits for the SNOW 3G, KASUMI and ZUC ciphers, and in bytes for other.

Have a look what the header file says:

uint32_t length;
/**< The message length, in bytes, of the
  * source buffer on which the cryptographic
  * operation will be computed.
  * This must be a multiple of the block size
  * if a block cipher is being used. This is
  * also the same as the result length.
  * @note
  * this field should be in bits.

This also gets built into the documentation available here:

Maybe that's why SNOW3G and ZUC were working for you, while AES-CTR did not?
The same applies to the offset field and to digest.data.offset and digest.data.length fields.

Please verify in your code how you set these all offset and length fields and check if you write the number of bits or the number of bytes in them.


             reply index

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-16 12:48 Dybkowski, AdamX [this message]
     [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
  -- strict thread matches above, loose matches on Subject: below --
2019-09-09  9:15 Naveen Kumar
2019-09-09 14:08 ` Trahe, Fiona
2019-09-09 14:27   ` 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=522B1A062D56224ABC0C6BDBCD64D9D369E6E7F2@IRSMSX103.ger.corp.intel.com \
    --to=adamx.dybkowski@intel.com \
    --cc=fiona.trahe@intel.com \
    --cc=naveen.kumar@commagility.com \
    --cc=users@dpdk.org \


* 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 \
	public-inbox-index users

Newsgroup available over NNTP:

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