xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Dag Nygren <dag@newtech.fi>
To: xen-devel@lists.xenproject.org
Subject: vtpmmgr compiled from from git strange output
Date: Mon, 08 Oct 2018 16:41:22 +0300	[thread overview]
Message-ID: <3151252.0ZAaMuH7Fy@dag.newtech.fi> (raw)


Just cloned master from git and compiled
stubdom/vtpmmgr and am getting weird output from it.

Like this:

TPM Manager - disk format 0
 root seal: zu; sector of 84: zu
 root: zu v=zu
 itree: 36; sector of 112: zu
 group: zu v=zu id=zu md=zu
 group seal: zu; 72 in parent: zu; sector of 5: zu
 vtpm: zu+zu; sector of 20: zu
INFO[VTPM]: disk_read_sector 0
INFO[VTPM]: disk_read_sector 1
load_root_pre: n/n
INFO[VTPM]: Assuming first time initialization.
INFO[TPM]: TPM2_CreatePrimary
INFO[VTPM]: SRK handle: 0x80000000
INFO[TPM]: TPM2_Create

Looking at the history in git it seems like the %zu was patched
quite dome time ago. Why was this done even if the
supporting c-lib doesn't seem to support it?

Am I missing something here?

And still vtpmmrg will not even touch the
disk image to persistantly save the Hash Key of
the vtpm:s.

Am I beating a dead horse here?


Xen-devel mailing list

                 reply	other threads:[~2018-10-08 13:41 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3151252.0ZAaMuH7Fy@dag.newtech.fi \
    --to=dag@newtech.fi \
    --cc=xen-devel@lists.xenproject.org \
    --subject='Re: vtpmmgr compiled from from git strange output' \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).