From: Tadeusz Struk <tadeusz.struk at intel.com>
To: tpm2@lists.01.org
Subject: [tpm2] Re: Error on TPM2 and Ubuntu 19.04
Date: Fri, 18 Oct 2019 11:25:46 -0700 [thread overview]
Message-ID: <e423eaa2-cf2e-6b3f-dff6-61726cb5c0bf@intel.com> (raw)
In-Reply-To: e7667319-4b47-4e22-8efd-4280c1ff7725@www.fastmail.com
[-- Attachment #1: Type: text/plain, Size: 1209 bytes --]
On 10/15/19 11:56 AM, Trey Weaver wrote:
> /*tpm2_createprimary -V -H o -g sha256 -G ecc -C primary2.ctx*//*
> */
> /*ObjectAttribute: 0x00030072*//*
> */
> /*ERROR on line: "182" in file: "tools/tpm2_createprimary.c":*//*
> */
> /*CreatePrimary Failed ! ErrorCode: 0x9a2*/
0x9a2 error means that the authorization failed. Seems like there is a
auth (password) setup for the owner hierarchy and by default clevis and
tpm2_createprimary use an empty auth. You can change the auth to an
empty one:
$ tpm2_changeauth -c o -p <OLD_PASS> ""
("") -means empty pass
and after that both the tpm2_createprimary and clevis encrypt tpm2
should work with the default.
> I am sure I have TPM2 setup correctly because things like tpm2_getrandom
> work fine.
tpm2_getrandom tool doesn't use the owner hierarchy thus it doesn't need
any authorization.
>
> tpm2_createprimary is version 3.1.3
>
> What can I do?
> Is there another tool beside clevis to auto unlock my drive that works
> better?
> Is there such a thing as a matched pair of tpm2-tool and clevis that I
> can get a package for?
I would follow what the clevis says. It looks like it requires tools v3
--
Tadeusz
next reply other threads:[~2019-10-18 18:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-18 18:25 Tadeusz Struk [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-10-16 16:18 [tpm2] Re: Error on TPM2 and Ubuntu 19.04 Oliver, Dario N
2019-10-15 23:07 Steven Clark
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=e423eaa2-cf2e-6b3f-dff6-61726cb5c0bf@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox