From: Tianjia Zhang <tianjia.zhang@linux.alibaba.com>
To: Ken Goldman <kgold@linux.ibm.com>,
linux-integrity@vger.kernel.org,
linux-security-module@vger.kernel.org
Subject: Re: [PATCH 0/2] tpm: use SM3 instead of SM3_256
Date: Wed, 20 Oct 2021 20:01:55 +0800 [thread overview]
Message-ID: <416a13af-beee-ac09-38ba-166a691a8482@linux.alibaba.com> (raw)
In-Reply-To: <c0768f9d-ef60-1a97-ec2d-a5e1130cbe03@linux.ibm.com>
Hi Ken,
On 10/20/21 6:26 AM, Ken Goldman wrote:
>
>
>
> On 10/11/2021 3:02 AM, Tianjia Zhang wrote:
>>
>> Thanks for your attention. This is really tricky. I will contact
>> trustedcomputinggroup first and give some suggestions, It would be
>> best if a more standard algorithm name can be used from the source of
>> the specification.
>
> This was discussed in the TCG's TPM WG in February, 2020. At the time,
> someone said that there was a possibility of a 512-bit version in the
> future.
>
> For TCG members:
>
> https://members.trustedcomputinggroup.org/wg/TPMWG/mail/thread/61442#136758
>
> My guess is that, since it's already in many TCG specs and code, TCG
> will want to leave it as is.
>
I got it. thanks for your information.
Best regards,
Tianjia
prev parent reply other threads:[~2021-10-20 12:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-09 13:08 [PATCH 0/2] tpm: use SM3 instead of SM3_256 Tianjia Zhang
2021-10-09 13:08 ` [PATCH 1/2] crypto: " Tianjia Zhang
2021-10-18 13:05 ` James Bottomley
2021-10-18 13:27 ` Jarkko Sakkinen
2021-10-18 13:32 ` James Bottomley
2021-10-18 13:41 ` Jarkko Sakkinen
2021-10-19 9:39 ` Tianjia Zhang
2021-10-19 9:35 ` Tianjia Zhang
2021-10-09 13:08 ` [PATCH 2/2] tpm: " Tianjia Zhang
2021-10-12 15:21 ` Jarkko Sakkinen
2021-10-14 9:46 ` Tianjia Zhang
2021-10-15 15:19 ` Jarkko Sakkinen
2021-10-18 2:37 ` Tianjia Zhang
2021-10-18 12:48 ` Jarkko Sakkinen
2021-10-09 13:29 ` [PATCH 0/2] " James Bottomley
2021-10-11 7:02 ` Tianjia Zhang
2021-10-19 22:26 ` Ken Goldman
2021-10-20 12:01 ` Tianjia Zhang [this message]
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=416a13af-beee-ac09-38ba-166a691a8482@linux.alibaba.com \
--to=tianjia.zhang@linux.alibaba.com \
--cc=kgold@linux.ibm.com \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-security-module@vger.kernel.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