From: Patrick Ohly <patrick.ohly@intel.com>
To: akuster808 <akuster808@gmail.com>
Cc: yocto@yoctoproject.org
Subject: Re: [meta-security][PATCH v2 0/9] tpm: virtual TPM for qemu
Date: Tue, 14 Feb 2017 12:21:41 +0100 [thread overview]
Message-ID: <1487071301.13854.330.camel@intel.com> (raw)
In-Reply-To: <b85dd671-0c0b-73f8-0c99-ce1f40bf8892@gmail.com>
On Fri, 2017-02-03 at 10:35 -0800, akuster808 wrote:
> On 2/3/17 12:46 AM, Patrick Ohly wrote:
> > I recently started using swtpm-native in combination with the qemu-tpm
> > patches to simulate a virtual TPM chip in qemu. The qemu-tpm patches
> > should go into OE-core, but currently usage is a bit cumbersome
> > (requires root privileges and manually starting swtpm before each
> > runqemu invocation), so at this time I only consider the meta-security
> > changes ready and useful enough for merging.
> >
> > Inside the virtual machine I used tpm-tools + trousers to set up
> > sealed keys for EVM, which required fixing a few things.
> >
> > These patches were based on Armin's swtpm+trousers version update
> > series which needs to be merged first to avoid merge conflicts.
> In staging
How often do you promote staging to master? Can this be done soon (like
this week)?
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
next prev parent reply other threads:[~2017-02-14 11:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-03 8:46 [meta-security][PATCH v2 0/9] tpm: virtual TPM for qemu Patrick Ohly
2017-02-03 8:46 ` [meta-security][PATCH v2 1/9] trousers: missing libtspi.so.1 in libtspi package Patrick Ohly
2017-02-03 8:46 ` [meta-security][PATCH v2 2/9] trousers: recommend tcsd Patrick Ohly
2017-02-03 8:46 ` [meta-security][PATCH v2 3/9] trousers: tcsd.conf must be owned tss:tss Patrick Ohly
2017-02-03 8:46 ` [meta-security][PATCH v2 4/9] swtpm: enable native and nativesdk flavors Patrick Ohly
2017-02-03 8:46 ` [meta-security][PATCH v2 5/9] swtpm: depends on tpm-tools Patrick Ohly
2017-02-03 8:46 ` [meta-security][PATCH v2 6/9] swtpm: fix compiler format warning Patrick Ohly
2017-02-03 8:46 ` [meta-security][PATCH v2 7/9] swtpm: cuse packageconfig Patrick Ohly
2017-02-03 8:46 ` [meta-security][PATCH v2 8/9] swtpm-wrappers: simplify using swtpm-native Patrick Ohly
2017-02-03 8:46 ` [meta-security][PATCH v2 9/9] swtpm: update to latest tip Patrick Ohly
2017-02-03 18:35 ` [meta-security][PATCH v2 0/9] tpm: virtual TPM for qemu akuster808
2017-02-14 11:21 ` Patrick Ohly [this message]
2017-02-15 15:35 ` akuster808
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=1487071301.13854.330.camel@intel.com \
--to=patrick.ohly@intel.com \
--cc=akuster808@gmail.com \
--cc=yocto@yoctoproject.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.