From: Florian Bauckholt <florian.bauckholt@cispa.de>
To: Rodolfo Giometti <giometti@enneenne.com>,
David Howells <dhowells@redhat.com>,
Jarkko Sakkinen <jarkko@kernel.org>,
Lukas Wunner <lukas@wunner.de>, Ignat Korchagin <ignat@linux.win>,
Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>
Cc: Paul Moore <paul@paul-moore.com>,
James Morris <jmorris@namei.org>,
"Serge E. Hallyn" <serge@hallyn.com>,
Hui Peng <benquike@gmail.com>,
Stefan Berger <stefanb@linux.ibm.com>, <keyrings@vger.kernel.org>,
<linux-crypto@vger.kernel.org>,
<linux-security-module@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <stable@vger.kernel.org>
Subject: Re: [PATCH 1/2] KEYS: fix signature length passed to KEYCTL_PKEY_VERIFY
Date: Thu, 19 Nov 2026 00:18:39 +0100 [thread overview]
Message-ID: <db5a384d-e833-4ab0-baf3-619717b39f60@cispa.de> (raw)
In-Reply-To: <0e20f799-e389-40d2-aaee-2f174748faae@enneenne.com>
On 11/17/26 14:21, Rodolfo Giometti wrote:
> The test suite of craf (https://github.com/giometti/crypto-afalg,
> test3008) hits this with RSA too: it cuts a genuine 256-byte RSA-2048
> PKCS#1 signature to 255 bytes and expects the verify to fail.
>
> Maybe it is worth saying so in the commit message, since this is going
> to stable?
Yes, I'll add it to v2 and link to your report.
> I'll send my Tested-by once test3008 has run 2000 times on a kernel
> with your patch applied.
Thanks. v2 is rebased but the code change is the same.
Florian
next prev parent reply other threads:[~2026-11-18 23:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-11 15:56 [PATCH 0/2] KEYS: two fixes for the asymmetric keyctl operations Florian Bauckholt via B4 Relay
2026-11-11 15:56 ` [PATCH 1/2] KEYS: fix signature length passed to KEYCTL_PKEY_VERIFY Florian Bauckholt via B4 Relay
2026-11-11 22:56 ` Jarkko Sakkinen
2026-11-17 13:21 ` Rodolfo Giometti
2026-11-18 23:18 ` Florian Bauckholt [this message]
2026-11-18 20:08 ` Stefan Berger
2026-11-18 20:28 ` Jarkko Sakkinen
2026-11-18 23:01 ` Florian Bauckholt
2026-11-11 15:56 ` [PATCH 2/2] KEYS: asymmetric: Fix PKCS#1 decryption of an empty message Florian Bauckholt via B4 Relay
2026-11-11 23:01 ` Jarkko Sakkinen
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=db5a384d-e833-4ab0-baf3-619717b39f60@cispa.de \
--to=florian.bauckholt@cispa.de \
--cc=benquike@gmail.com \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=giometti@enneenne.com \
--cc=herbert@gondor.apana.org.au \
--cc=ignat@linux.win \
--cc=jarkko@kernel.org \
--cc=jmorris@namei.org \
--cc=keyrings@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=paul@paul-moore.com \
--cc=serge@hallyn.com \
--cc=stable@vger.kernel.org \
--cc=stefanb@linux.ibm.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
all inboxes | Powered by JetHome®