From: Roberto Sassu <roberto.sassu@huawei.com>
To: tpmdd-devel@lists.sourceforge.net
Cc: linux-ima-devel@lists.sourceforge.net,
linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org,
Roberto Sassu <roberto.sassu@huawei.com>
Subject: [PATCH 0/2] Update PCR read code
Date: Fri, 23 Jun 2017 15:41:55 +0200 [thread overview]
Message-ID: <20170623134157.30399-1-roberto.sassu@huawei.com> (raw)
This patch set updates tpm2_pcr_read(), to build the PCR read command
buffer with tpm_buf functions, which offer protection against buffer
overflow.
It also removes duplicate code in tpm2_do_selftest(), and replaces it with
a call to tpm2_pcr_read().
The previous version of the patches can be found at the URLs:
https://sourceforge.net/p/tpmdd/mailman/message/35905413/
https://sourceforge.net/p/tpmdd/mailman/message/35905415/
The version number has not been incremented from 3 to 4, since this
is considered as a new patch set, not providing the same functionality
of the set the patches were originally part of.
Changelog
- PCR code changes are applied directly to tpm2_pcr_read()
- removed tpm2_pcr_read_in structure
- modified size of digest array in tpm2_pcr_read_out structure
Roberto Sassu (2):
tpm: use tpm_buf functions in tpm2_pcr_read()
tpm: use tpm2_pcr_read() in tpm2_do_selftest()
drivers/char/tpm/tpm2-cmd.c | 89 +++++++++++++++------------------------------
1 file changed, 30 insertions(+), 59 deletions(-)
--
2.9.3
next reply other threads:[~2017-06-23 13:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-23 13:41 Roberto Sassu [this message]
2017-06-23 13:41 ` [PATCH 1/2] tpm: use tpm_buf functions in tpm2_pcr_read() Roberto Sassu
2017-06-28 22:18 ` Jarkko Sakkinen
2017-06-29 19:54 ` Jarkko Sakkinen
2017-06-23 13:41 ` [PATCH 2/2] tpm: use tpm2_pcr_read() in tpm2_do_selftest() Roberto Sassu
2017-06-28 22:19 ` Jarkko Sakkinen
2017-06-29 19:56 ` [tpmdd-devel] " 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=20170623134157.30399-1-roberto.sassu@huawei.com \
--to=roberto.sassu@huawei.com \
--cc=linux-ima-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=tpmdd-devel@lists.sourceforge.net \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).