Linux cryptographic layer development
 help / color / mirror / Atom feed
From: Herbert Xu <herbert@gondor.apana.org.au>
To: "Jérémy Jean" <Jeremy.Jean@oss.cyber.gouv.fr>
Cc: Lukas Wunner <lukas@wunner.de>, Ignat Korchagin <ignat@linux.win>,
	"David S. Miller" <davem@davemloft.net>,
	linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] crypto: rsassa-pkcs1: fix undersized key handling
Date: Fri, 11 Sep 2026 15:28:06 +1000	[thread overview]
Message-ID: <aqORZi129t_AHaku@gondor.apana.org.au> (raw)
In-Reply-To: <20260826103744.1554131-1-Jeremy.Jean@oss.cyber.gouv.fr>

On Wed, Aug 26, 2026 at 10:37:42AM +0000, Jérémy Jean wrote:
> PKCS#1 v1.5 requires an encoded message of at least 11 bytes. The
> signing and verification functions do not reject smaller RSA modulus
> sizes reported by the child implementation.
> 
> This series include two patches due to integer underflows:
> * one in the signing function that can write OOB,
> * one in the verification function that can read 1 byte OOB.
> 
> Jérémy Jean (2):
>   crypto: rsassa-pkcs1: reject undersized keys when signing
>   crypto: rsassa-pkcs1: reject undersized keys when verifying
> 
>  crypto/rsassa-pkcs1.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> -- 
> 2.47.3

All applied.  Thanks.
-- 
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt

      parent reply	other threads:[~2026-09-11  5:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-26 10:37 [PATCH 0/2] crypto: rsassa-pkcs1: fix undersized key handling Jérémy Jean
2026-08-26 10:37 ` [PATCH 1/2] crypto: rsassa-pkcs1: reject undersized keys when signing Jérémy Jean
2026-08-26 15:44   ` Sudhakar Kuppusamy
2026-08-26 10:37 ` [PATCH 2/2] crypto: rsassa-pkcs1: reject undersized keys when verifying Jérémy Jean
2026-08-26 15:44   ` Sudhakar Kuppusamy
2026-09-11  5:28 ` Herbert Xu [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=aqORZi129t_AHaku@gondor.apana.org.au \
    --to=herbert@gondor.apana.org.au \
    --cc=Jeremy.Jean@oss.cyber.gouv.fr \
    --cc=davem@davemloft.net \
    --cc=ignat@linux.win \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lukas@wunner.de \
    /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