From: Eric Biggers <ebiggers@kernel.org>
To: linux-crypto@vger.kernel.org, Herbert Xu <herbert@gondor.apana.org.au>
Cc: Corentin Labbe <clabbe@baylibre.com>,
Stafford Horne <shorne@gmail.com>,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/4] crypto: crypto_user reporting fixes and cleanups
Date: Sat, 3 Nov 2018 14:55:59 -0700 [thread overview]
Message-ID: <20181103215603.16250-1-ebiggers@kernel.org> (raw)
This series fixes all the information leaks in crypto_user reporting,
removes some redundant reporting functions, and makes some changes to
reduce the chance of similar information leaks in the future. Patch 2
is based on a patch already sent by Corentin Labbe, but it was
incomplete so I fixed it.
Corentin Labbe (1):
crypto: crypto_user_stat - Zeroize whole structure given to user space
Eric Biggers (3):
crypto: crypto_user - fix leaking uninitialized memory to userspace
crypto: crypto_user - remove redundant reporting functions
crypto: crypto_user - clean up report structure copying
crypto/ablkcipher.c | 32 ++++------
crypto/acompress.c | 10 +---
crypto/aead.c | 14 ++---
crypto/ahash.c | 12 ++--
crypto/akcipher.c | 11 ++--
crypto/blkcipher.c | 16 ++---
crypto/crypto_user_base.c | 95 +++++------------------------
crypto/crypto_user_stat.c | 123 ++++++++++++++------------------------
crypto/kpp.c | 10 +---
crypto/rng.c | 12 ++--
crypto/scompress.c | 11 ++--
crypto/shash.c | 12 ++--
crypto/skcipher.c | 15 ++---
13 files changed, 116 insertions(+), 257 deletions(-)
--
2.19.1
next reply other threads:[~2018-11-03 21:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-03 21:55 Eric Biggers [this message]
2018-11-03 21:56 ` [PATCH 1/4] crypto: crypto_user - fix leaking uninitialized memory to userspace Eric Biggers
2018-11-03 21:56 ` [PATCH 2/4] crypto: crypto_user_stat - Zeroize whole structure given to user space Eric Biggers
2018-11-03 21:56 ` [PATCH 3/4] crypto: crypto_user - remove redundant reporting functions Eric Biggers
2018-11-03 21:56 ` [PATCH 4/4] crypto: crypto_user - clean up report structure copying Eric Biggers
2018-11-09 9:46 ` [PATCH 0/4] crypto: crypto_user reporting fixes and cleanups 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=20181103215603.16250-1-ebiggers@kernel.org \
--to=ebiggers@kernel.org \
--cc=clabbe@baylibre.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shorne@gmail.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
Powered by JetHome