From: Eric Biggers <ebiggers@kernel.org>
To: linux-crypto@vger.kernel.org, Herbert Xu <herbert@gondor.apana.org.au>
Cc: keyrings@vger.kernel.org, Vitaly Chikunov <vt@altlinux.org>,
Denis Kenzior <denkenz@gmail.com>
Subject: [PATCH v2 0/5] crypto: rsa-pkcs1pad fixes
Date: Tue, 18 Jan 2022 16:13:01 -0800 [thread overview]
Message-ID: <20220119001306.85355-1-ebiggers@kernel.org> (raw)
This series fixes some bugs in rsa-pkcs1pad.
Changed v1 => v2:
- Added patch "crypto: rsa-pkcs1pad - only allow with rsa"
(previously was a standalone patch)
- Added patch "crypto: rsa-pkcs1pad - restore signature length check"
Eric Biggers (5):
crypto: rsa-pkcs1pad - only allow with rsa
crypto: rsa-pkcs1pad - correctly get hash from source scatterlist
crypto: rsa-pkcs1pad - restore signature length check
crypto: rsa-pkcs1pad - fix buffer overread in
pkcs1pad_verify_complete()
crypto: rsa-pkcs1pad - use clearer variable names
crypto/rsa-pkcs1pad.c | 38 +++++++++++++++++++++++---------------
1 file changed, 23 insertions(+), 15 deletions(-)
--
2.34.1
next reply other threads:[~2022-01-19 0:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-19 0:13 Eric Biggers [this message]
2022-01-19 0:13 ` [PATCH v2 1/5] crypto: rsa-pkcs1pad - only allow with rsa Eric Biggers
2022-01-19 0:13 ` [PATCH v2 2/5] crypto: rsa-pkcs1pad - correctly get hash from source scatterlist Eric Biggers
2022-01-19 0:13 ` [PATCH v2 3/5] crypto: rsa-pkcs1pad - restore signature length check Eric Biggers
2022-01-19 0:13 ` [PATCH v2 4/5] crypto: rsa-pkcs1pad - fix buffer overread in pkcs1pad_verify_complete() Eric Biggers
2022-01-19 0:13 ` [PATCH v2 5/5] crypto: rsa-pkcs1pad - use clearer variable names Eric Biggers
2022-01-28 6:26 ` [PATCH v2 0/5] crypto: rsa-pkcs1pad fixes Herbert Xu
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=20220119001306.85355-1-ebiggers@kernel.org \
--to=ebiggers@kernel.org \
--cc=denkenz@gmail.com \
--cc=herbert@gondor.apana.org.au \
--cc=keyrings@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=vt@altlinux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.