From: Andreas Sommer <AndiDog@web.de>
To: Martin Schneider <martincschneider@googlemail.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: vTPM Support
Date: Tue, 26 Jan 2010 12:48:46 +0100 [thread overview]
Message-ID: <4B5ED69E.8070309@web.de> (raw)
In-Reply-To: <690347541001260210xf1b2648j7584d95e7c4a4713@mail.gmail.com>
Martin Schneider wrote:
> Dear list,
>
> I wonder if there is a document that describes the level of support of
> virtual Trusted Computing functionality of the current version of XEN.
> Unfortunately I couldn't find such a document.
>
> Thank you for your help.
>
> Best regards,
> Martin
There's a good tutorial on building vTPM support for Xen at
http://cybione.org/~cdidier/blog/200812020841.html
<http://cybione.org/%7Ecdidier/blog/200812020841.html>. You can either
use a physical TPM or the TPM emulator (of course unsafe) from
sourceforge. However I don't know how robust the vTPM implementation is...
Regards,
Andreas
next prev parent reply other threads:[~2010-01-26 11:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-26 10:10 vTPM Support Martin Schneider
2010-01-26 11:48 ` Andreas Sommer [this message]
2010-01-26 12:23 ` Martin Schneider
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=4B5ED69E.8070309@web.de \
--to=andidog@web.de \
--cc=martincschneider@googlemail.com \
--cc=xen-devel@lists.xensource.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;
as well as URLs for NNTP newsgroup(s).