DPDK patches and discussions
 help / color / mirror / Atom feed
From: Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>
To: "Ji, Kai" <kai.ji@intel.com>
Cc: Anoob Joseph <anoobj@marvell.com>, "dev@dpdk.org" <dev@dpdk.org>,
	Akhil Goyal <gakhil@marvell.com>,
	Fan Zhang <fanzhang.oss@gmail.com>,
	Shally Verma <shallyv@marvell.com>,
	Kanaka Durga Kotamarthy <kkotamarthy@marvell.com>,
	Ayuj Verma <ayverma@marvell.com>,
	"Kusztal, ArkadiuszX" <arkadiuszx.kusztal@intel.com>
Subject: RE: [PATCH] test/crypto: fix RSA decrypt op validation
Date: Thu, 19 Jun 2025 09:43:49 +0000	[thread overview]
Message-ID: <BY3PR18MB4705C949AE6479C7FC232E31CB7DA@BY3PR18MB4705.namprd18.prod.outlook.com> (raw)
In-Reply-To: <CO1PR18MB47144653AC9A8DF6E8B1C697CB72A@CO1PR18MB4714.namprd18.prod.outlook.com>

Hi Kai Ji,
Debugged it using openssl source code used in these distros and the failure found due to below
Implicit rejection added in PKCS padding.

https://github.com/openssl/openssl/pull/13817/commits/3b99dcb1a6df6853581d3035c6d9a23a831716bb

As part of the above fix, rsa_ossl_private_decrypt() would additionally need private exponent
rsa->d, assuming that d is already part of RSA session, to derive kdk used in implicit rejection.
We did not have it in CRT test vectors today. I'll send patch to fix these.

Thanks,
Gowrishankar
> 
> Hi Kai Ji,
> >
> > Hi Gowrishankar,
> >
> > Thanks for reach out, I don't have those environments setup on my end,
> > but Ubuntu 20.04 and RHEL8  are old but still common LTS packages.
> > Are you able to dump the actual msg buffer ?
> >
> 
> RSA_private_decrypt fails and return code is -1. Output buffer is untouched.
> 
> I dumped error code of it:
> error:04067084:rsa routines:rsa_ossl_public_decrypt:data too large for
> modulus
> 
> When I used same openssl library that I compiled, no error is seen. Also, public
> decrypt function is called, but it should be private decrypt to be called.
> 
> JFYI end of life for full support already over for the above distros. Not sure if
> the Openssl 1.1.1 in them need some fix for above.
> 
> Thanks,
> Gowrishankar
> 


      reply	other threads:[~2025-06-19  9:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-10 10:44 Gowrishankar Muthukrishnan
2025-05-28  8:38 ` Gowrishankar Muthukrishnan
2025-06-12 10:33 ` Gowrishankar Muthukrishnan
2025-06-16 14:17   ` Ji, Kai
2025-06-18 16:04     ` Gowrishankar Muthukrishnan
2025-06-19  9:43       ` Gowrishankar Muthukrishnan [this message]

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=BY3PR18MB4705C949AE6479C7FC232E31CB7DA@BY3PR18MB4705.namprd18.prod.outlook.com \
    --to=gmuthukrishn@marvell.com \
    --cc=anoobj@marvell.com \
    --cc=arkadiuszx.kusztal@intel.com \
    --cc=ayverma@marvell.com \
    --cc=dev@dpdk.org \
    --cc=fanzhang.oss@gmail.com \
    --cc=gakhil@marvell.com \
    --cc=kai.ji@intel.com \
    --cc=kkotamarthy@marvell.com \
    --cc=shallyv@marvell.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).