From: Denis Kenzior <denkenz@gmail.com>
To: Eric Biggers <ebiggers@kernel.org>,
keyrings@vger.kernel.org, David Howells <dhowells@redhat.com>,
Jarkko Sakkinen <jarkko@kernel.org>
Cc: Marcel Holtmann <marcel@holtmann.org>,
James Morris <james.morris@microsoft.com>,
linux-crypto@vger.kernel.org
Subject: Re: [PATCH 0/3] KEYS: fixes for asym_tpm keys
Date: Fri, 14 Jan 2022 08:54:22 -0600 [thread overview]
Message-ID: <b21cf62d-92d1-5180-a303-e55714683d13@gmail.com> (raw)
In-Reply-To: <20220113235440.90439-1-ebiggers@kernel.org>
Hi Eric,
On 1/13/22 17:54, Eric Biggers wrote:
> This series fixes some bugs in asym_tpm.c.
>
> Eric Biggers (3):
> KEYS: asym_tpm: fix buffer overreads in extract_key_parameters()
> KEYS: asym_tpm: fix incorrect comment
> KEYS: asym_tpm: rename derive_pub_key()
>
> crypto/asymmetric_keys/asym_tpm.c | 44 +++++++++++++++++++------------
> 1 file changed, 27 insertions(+), 17 deletions(-)
>
>
> base-commit: feb7a43de5ef625ad74097d8fd3481d5dbc06a59
>
For the series:
Reviewed-By: Denis Kenzior <denkenz@gmail.com>
Regards,
-Denis
next prev parent reply other threads:[~2022-01-14 14:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-13 23:54 [PATCH 0/3] KEYS: fixes for asym_tpm keys Eric Biggers
2022-01-13 23:54 ` [PATCH 1/3] KEYS: asym_tpm: fix buffer overreads in extract_key_parameters() Eric Biggers
2022-01-15 21:40 ` Jarkko Sakkinen
2022-01-19 0:59 ` Eric Biggers
2022-01-26 14:21 ` Jarkko Sakkinen
2022-01-26 14:22 ` Jarkko Sakkinen
2022-01-28 19:00 ` Eric Biggers
2022-02-08 9:30 ` Jarkko Sakkinen
2022-01-13 23:54 ` [PATCH 2/3] KEYS: asym_tpm: fix incorrect comment Eric Biggers
2022-01-15 19:12 ` Jarkko Sakkinen
2022-01-13 23:54 ` [PATCH 3/3] KEYS: asym_tpm: rename derive_pub_key() Eric Biggers
2022-01-15 19:09 ` Jarkko Sakkinen
2022-01-14 14:54 ` Denis Kenzior [this message]
2022-01-15 21:42 ` [PATCH 0/3] KEYS: fixes for asym_tpm keys 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=b21cf62d-92d1-5180-a303-e55714683d13@gmail.com \
--to=denkenz@gmail.com \
--cc=dhowells@redhat.com \
--cc=ebiggers@kernel.org \
--cc=james.morris@microsoft.com \
--cc=jarkko@kernel.org \
--cc=keyrings@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=marcel@holtmann.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 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).