From: Roberts, William C <william.c.roberts at intel.com>
To: tpm2@lists.01.org
Subject: [tpm2] Re: Is there a way to get the name for an NV index in tpm2_tools?
Date: Mon, 25 Nov 2019 16:47:07 +0000 [thread overview]
Message-ID: <476DC76E7D1DF2438D32BFADF679FC5649E47E0A@ORSMSX101.amr.corp.intel.com> (raw)
In-Reply-To: CAOCvsS=YPo=PNS+=XT1Fr6fCWWeY3NonQbL35dvGzN1xUS6NMw@mail.gmail.com
[-- Attachment #1: Type: text/plain, Size: 971 bytes --]
tpm2_getcapability -c primary.ctx:
name: 000b914a1abc3f6b71166e4b8d3a02ee338524bb5b82a7c9e1a59f28dc97f7f2fd0c
qualified name: 000bdb4f165a0db93bc1cccbc5266f69ceaafe1bf96bcab11ca73d6f155a15a66591
name-alg:
value: sha256
raw: 0xb
<snip>
What version of the tools are you on as reported by the -V option?
> -----Original Message-----
> From: Steven Clark [mailto:davolfman(a)gmail.com]
> Sent: Friday, November 22, 2019 4:04 PM
> To: Roberts, William C <william.c.roberts(a)intel.com>
> Cc: tpm2(a)lists.01.org
> Subject: Re: [tpm2] Is there a way to get the name for an NV index in
> tpm2_tools?
>
> That's what I thought, but it doesn't. I provides the handle, attributes, and policy
> hash, but not the Name.
> If I read the spec right the contents of the index are part of the hash so I don't
> think this is even enough information to compute the Name. And manually
> computing a Name is beyond my trust in my own abilities right now.
next reply other threads:[~2019-11-25 16:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-25 16:47 Roberts, William C [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-11-27 23:27 [tpm2] Re: Is there a way to get the name for an NV index in tpm2_tools? Steven Clark
2019-11-25 23:52 Roberts, William C
2019-11-25 23:02 Roberts, William C
2019-11-25 16:56 Steven Clark
2019-11-22 22:03 Steven Clark
2019-11-21 21:57 Roberts, William C
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=476DC76E7D1DF2438D32BFADF679FC5649E47E0A@ORSMSX101.amr.corp.intel.com \
--to=tpm2@lists.01.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.