From: Thibaut Sautereau <thibaut.sautereau at clip-os.org>
To: tpm2@lists.01.org
Subject: Re: [tpm2] Issues experimenting with tpm2-tools and keyctl trusted keys
Date: Wed, 23 Jan 2019 14:56:57 +0100 [thread overview]
Message-ID: <20190123135657.GB12820@gandi.net> (raw)
In-Reply-To: 9F48E1A823B03B4790B7E6E69430724D014B4C36D5@exch2010c.sit.fraunhofer.de
[-- Attachment #1: Type: text/plain, Size: 580 bytes --]
On Wed, Jan 23, 2019 at 01:11:20PM +0000, Fuchs, Andreas wrote:
> have you tried running the same sequences but using tpm2_create
> instead of "keyctl new" and tpm2_unseal instead of "keyctl load" ?
> Just to make sure that the TPM side of things is working ok ?
Yes, using tpm2_create instead of "keyctl new" and tpm2_load+tpm2_unseal
(exclusively with handles) instead of "keyctl load" works perfectly.
> Then it would be narrowed down to finding the diff between the basic
> commands and how keyctl uses them.
Right.
--
Thibaut Sautereau
CLIP OS developer
next reply other threads:[~2019-01-23 13:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-23 13:56 Thibaut Sautereau [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-01-23 13:11 [tpm2] Issues experimenting with tpm2-tools and keyctl trusted keys Fuchs, Andreas
2019-01-23 12:59 Thibaut Sautereau
2019-01-23 9:36 Javier Martinez Canillas
2019-01-21 8:16 Thibaut Sautereau
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=20190123135657.GB12820@gandi.net \
--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