From: Kouichi Yasaki <yasaki.kouichi@jp.fujitsu.com>
To: xen-devel@lists.xensource.com
Subject: [PATCH][VTPM]fix GetCapabilityOwner function
Date: Sat, 29 Dec 2007 01:14:34 +0900 [thread overview]
Message-ID: <477520EA.2030806@jp.fujitsu.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 385 bytes --]
Hi,
GetCapabilityOwner function's behavior of vtpm is different from that of
real tpm device. By the difference, TPM Manager on HVM domain could not
detect whether TPM device has an owner or not.
[TPM Manager]
http://sourceforge.net/projects/tpmmanager
Attached patch fix the difference.
Signed-off-by: Kouichi YASAKI <yasaki.kouichi@jp.fujitsu.com>
Thanks
Kouichi YASAKI
[-- Attachment #2: capability.patch --]
[-- Type: text/plain, Size: 1281 bytes --]
diff -r 7fbc521b07a9 tools/vtpm/tpm_emulator.patch
--- a/tools/vtpm/tpm_emulator.patch Thu Dec 27 13:00:40 2007 +0000
+++ b/tools/vtpm/tpm_emulator.patch Fri Dec 28 22:59:52 2007 +0900
@@ -547,6 +547,21 @@ diff -uprN orig/tpm_emulator-0.4/README
Installation
--------------------------------------------------------------------------
The compilation and installation process uses the build environment for
+diff -uprN orig/tpm_emulator-0.4/tpm/tpm_capability.c tpm_emulator/tpm/tpm_capability.c
+--- orig/tpm_emulator-0.4/tpm/tpm_capability.c 2006-06-23 19:37:07.000000000 +0900
++++ tpm_emulator/tpm/tpm_capability.c 2007-12-28 22:50:19.000000000 +0900
+@@ -701,7 +701,10 @@ TPM_RESULT TPM_GetCapabilityOwner(TPM_VE
+ TPM_RESULT res;
+
+ info("TPM_GetCapabilityOwner()");
+-
++
++ if (!tpmData.permanent.flags.owned) {
++ return TPM_NOSRK;
++ }
+ /* Verify owner authorization */
+ res = tpm_verify_auth(auth1, tpmData.permanent.data.ownerAuth, TPM_KH_OWNER);
+ if (res != TPM_SUCCESS) return res;
diff -uprN orig/tpm_emulator-0.4/tpm/tpm_cmd_handler.c tpm_emulator/tpm/tpm_cmd_handler.c
--- orig/tpm_emulator-0.4/tpm/tpm_cmd_handler.c 2006-06-23 19:37:07.000000000 +0900
+++ tpm_emulator/tpm/tpm_cmd_handler.c 2007-09-12 20:23:00.000000000 +0900
[-- Attachment #3: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
reply other threads:[~2007-12-28 16:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=477520EA.2030806@jp.fujitsu.com \
--to=yasaki.kouichi@jp.fujitsu.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 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.