From: jarkko.sakkinen@linux.intel.com (Jarkko Sakkinen)
To: linux-security-module@vger.kernel.org
Subject: [PATCH v2] tpm: consolidate the TPM startup code
Date: Thu, 22 Jun 2017 12:02:56 +0200 [thread overview]
Message-ID: <20170622100256.ehlcwkjp4iduxkbm@linux.intel.com> (raw)
In-Reply-To: <1ff1a552-15a9-d8a6-3bcd-3c0f9ff6d71e@linux.vnet.ibm.com>
On Wed, Jun 21, 2017 at 07:04:53AM -0400, Stefan Berger wrote:
> On 06/21/2017 03:31 AM, Jarkko Sakkinen wrote:
> > Consolidated all the "manual" TPM startup code to a single function
> > in order to make code flows a bit cleaner and migrate to tpm_buf.
> >
> > Signed-off-by: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
>
> Tested-by: Stefan Berger <stefanb@linux.vnet.ibm.com>
>
>
> FYI:
> swtpm chardev --vtpm-proxy --tpmstate dir=/tmp --log level=1 --tpm2
> swtpm chardev --vtpm-proxy --tpmstate dir=/tmp --log level=1
Thank you! I will also add your Tested-by to
- https://patchwork.kernel.org/patch/9799059/
- https://patchwork.kernel.org/patch/9799057/
I'm in the process of enhancing my BuildRoot enviroment with libtpms and
swtpm packages. My first target is TPM 1.2 test environment by using
tpm_vtpm_proxy driver.
http://git.infradead.org/users/jjs/buildroot-tpmdd.git
Should be easy as you have nicely autooled projects :-)
/Jarkko
--
To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2017-06-22 10:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-21 7:31 [PATCH v2] tpm: consolidate the TPM startup code Jarkko Sakkinen
2017-06-21 11:04 ` Stefan Berger
2017-06-22 10:02 ` Jarkko Sakkinen [this message]
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=20170622100256.ehlcwkjp4iduxkbm@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=linux-security-module@vger.kernel.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).