DPDK usage discussions
 help / color / mirror / Atom feed
From: "Kusztal, ArkadiuszX" <arkadiuszx.kusztal@intel.com>
To: Balakrishnan K <Balakrishnan.K1@tatacommunications.com>,
	"users@dpdk.org" <users@dpdk.org>
Subject: RE: how to use crypto openssl PMD for asymmetric encryption and decryption
Date: Tue, 24 May 2022 09:13:50 +0000	[thread overview]
Message-ID: <PH0PR11MB5013E6CD6BD9C5F4A6CDD1BB9FD79@PH0PR11MB5013.namprd11.prod.outlook.com> (raw)
In-Reply-To: <PSAPR04MB55167EE7F28A38EE575504DAD6D79@PSAPR04MB5516.apcprd04.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 3949 bytes --]

I should use

debug_hexdump(stdout, "encrypted message", asym_op->rsa.cipher.data,

                      asym_op->rsa.cipher.length);

to check the encrypted message for the input given?

Yes, currently it works this way. The same way output for decryption will be placed in asym_op->rsa.message.data and input in asym_op->rsa.cipher.data.
More explanations can be found in rte_crypto_asym.h file
https://doc.dpdk.org/api/structrte__crypto__rsa__op__param.html.

From: Balakrishnan K <Balakrishnan.K1@tatacommunications.com>
Sent: Tuesday, May 24, 2022 7:24 AM
To: Kusztal, ArkadiuszX <arkadiuszx.kusztal@intel.com>; users@dpdk.org
Subject: RE: how to use crypto openssl PMD for asymmetric encryption and decryption

Hi Arek,
   Thanks for quick response.
I am using resulted output vector to verify the encrypted message.

I thought the encrypted data will be in the asym_op->rsa.message.data after rte_cryptodev_enqueue_burst and rte_cryptodev_enqueue_burst call with operation type RTE_CRYPTO_ASYM_OP_ENCRYPT.

So ,I checked the hex_dump of asym_op->rsa.message.data.



Code snippet:

asym_op = result_op->asym;

debug_hexdump(stdout, "encrypted message", asym_op->rsa.message.data,

                      asym_op->rsa.message.length);







Encrypted data will be placed in asym_op->rsa.cipher.data after crypto operation is my understanding is correct ?

I should use

debug_hexdump(stdout, "encrypted message", asym_op->rsa.cipher.data,

                      asym_op->rsa.cipher.length);

to check the encrypted message for the input given?





Regards,

Bala



From: Kusztal, ArkadiuszX <arkadiuszx.kusztal@intel.com<mailto:arkadiuszx.kusztal@intel.com>>
Sent: 23 May 2022 18:15
To: Balakrishnan K <Balakrishnan.K1@tatacommunications.com<mailto:Balakrishnan.K1@tatacommunications.com>>; users@dpdk.org<mailto:users@dpdk.org>
Subject: RE: how to use crypto openssl PMD for asymmetric encryption and decryption


CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
Hi Bala,

Ciphertext will be written into asym_op->rsa.cipher.data (not message.data) by the PMD, here you are using same address for both hex dumps.
Although there is a bug in debug_hexdump in this function which may cause this confusion.

Plus, the test you are referring is PWCT test (Pairwise conditional test) -> it will encrypt, then decrypt.
Please take a look into this comment in queue_ops_rsa_enc_dec function:
/* Use the resulted output as decryption Input vector*
So above this line there is an encryption part.
Below is decryption.

Regards,
Arek

From: Balakrishnan K <Balakrishnan.K1@tatacommunications.com<mailto:Balakrishnan.K1@tatacommunications.com>>
Sent: Monday, May 23, 2022 1:33 PM
To: users@dpdk.org<mailto:users@dpdk.org>
Subject: how to use crypto openssl PMD for asymmetric encryption and decryption

Hi All,
   I am new to dpdk. Planning to use openssl crypto PMD for encrypting/decrypting  the packets.
Couldn't find much documents on openssl PMD for asymmetric encryption/decryption.
Any one please point me in the right document.

I have tried to run the test cases wrote for asymmetric crypto using openssl virtual PMD.
But the output of particular test case is same after the encryption done.

File : app/test/test_cryptodev_asym.c
Test executable: ./app/test/dpdk-test
Test case : test_rsa_enc_dec

Input given to encryption:
message at [0x1894e60], len=20
00000000: F8 BA 1A 55 D0 2F 85 AE 96 7B B6 2F B6 CD A8 EB | ...U./...{./....
00000010: 7E 78 A0 50                                     | ~x.P

After processing the output also looks like same :
encrypted message exist at [0x1894e60], len=20
00000000: F8 BA 1A 55 D0 2F 85 AE 96 7B B6 2F B6 CD A8 EB | ...U./...{./....
00000010: 7E 78 A0 50


Regards,
Bala

[-- Attachment #2: Type: text/html, Size: 10715 bytes --]

  reply	other threads:[~2022-05-24  9:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-23 11:33 Balakrishnan K
2022-05-23 12:45 ` Kusztal, ArkadiuszX
2022-05-24  5:23   ` Balakrishnan K
2022-05-24  9:13     ` Kusztal, ArkadiuszX [this message]
2022-05-24 12:12       ` Balakrishnan K
2022-05-25 10:08         ` Balakrishnan K
2022-05-25 10:43           ` Kusztal, ArkadiuszX
2022-05-30 11:58             ` Balakrishnan K
2022-05-30 12:22               ` Kusztal, ArkadiuszX
2022-05-31  6:13                 ` Balakrishnan K
2022-05-31  7:30                   ` Kusztal, ArkadiuszX
2022-06-06 12:31                     ` Balakrishnan K
2022-06-07  4:33                       ` Kusztal, ArkadiuszX

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=PH0PR11MB5013E6CD6BD9C5F4A6CDD1BB9FD79@PH0PR11MB5013.namprd11.prod.outlook.com \
    --to=arkadiuszx.kusztal@intel.com \
    --cc=Balakrishnan.K1@tatacommunications.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).