From: Coly Li <colyli@suse.de>
To: jejb@linux.ibm.com
Cc: Stefan Berger <stefanb@linux.ibm.com>,
keyrings@vger.kernel.org, linux-kernel@vger.kernel.org,
Dan Williams <dan.j.williams@intel.com>,
Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>,
Mimi Zohar <zohar@linux.ibm.com>
Subject: Re: [PATCH RESEND] docs: update trusted-encrypted.rst
Date: Mon, 17 Aug 2020 00:57:56 +0800 [thread overview]
Message-ID: <f9d4c4a9-5059-eae2-bc89-51f16e8ca4d9@suse.de> (raw)
In-Reply-To: <1597595769.8344.7.camel@linux.ibm.com>
On 2020/8/17 00:36, James Bottomley wrote:
> On Sun, 2020-08-16 at 12:06 -0400, Stefan Berger wrote:
> [...]
>> A note in this file states this:
>>
>> Note: When using a TPM 2.0 with a persistent key with handle
>> 0x81000001, append 'keyhandle=0x81000001' to statements between
>> quotes, such as "new 32 keyhandle=0x81000001".
>>
>> Now if someone was (still) interested in TPM 1.2 then the below
>> changes you are proposing wouldn't work for them. Maybe you should
>> adapt the note to state that these keyhandle=... should be removed
>> for the TPM 1.2 case.
>
> Actually, I also have a plan to match what userspace does and simply
> assume a keyhandle of 40000001 (generate an EC Storage Primary Key on
> the fly) if it's not specified, which will make the TPM1.2 and 2.0
> versions of this the same. Unfortunately the necessary precursor
> patches are taking an age to get upstream.
Hi James,
Do you have a plan to push such patches into upstream soon? If yes than
I may wait for your patch and withdraw this one.
Thanks.
Coly Li
next prev parent reply other threads:[~2020-08-16 16:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-15 7:51 [PATCH RESEND] docs: update trusted-encrypted.rst Coly Li
2020-08-16 16:06 ` Stefan Berger
2020-08-16 16:36 ` James Bottomley
2020-08-16 16:57 ` Coly Li [this message]
2020-08-16 17:12 ` James Bottomley
2020-08-16 17:15 ` Coly Li
2020-08-18 15:44 ` Jarkko Sakkinen
2020-08-18 16:19 ` James Bottomley
2020-08-19 21:01 ` Jarkko Sakkinen
2020-08-16 17:01 ` Coly Li
2020-08-16 17:08 ` James Bottomley
2020-08-16 17:22 ` Coly Li
2020-08-16 17:05 ` Coly Li
2020-08-15 12:46 colyli
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=f9d4c4a9-5059-eae2-bc89-51f16e8ca4d9@suse.de \
--to=colyli@suse.de \
--cc=dan.j.williams@intel.com \
--cc=jarkko.sakkinen@linux.intel.com \
--cc=jejb@linux.ibm.com \
--cc=keyrings@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stefanb@linux.ibm.com \
--cc=zohar@linux.ibm.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 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).