From: "Linux regression tracking (Thorsten Leemhuis)" <regressions@leemhuis.info>
To: "Limonciello, Mario" <mario.limonciello@amd.com>,
"Jason A. Donenfeld" <Jason@zx2c4.com>,
regressions@lists.linux.dev, linux-integrity@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: Jarkko Sakkinen <jarkko@kernel.org>,
James Bottomley <James.Bottomley@hansenpartnership.com>
Subject: Re: [PATCH RFC] tpm: disable hwrng for known-defective AMD RNGs
Date: Sat, 11 Feb 2023 16:15:56 +0100 [thread overview]
Message-ID: <08063f18-95de-bf2d-4f03-8b72b2eac7c4@leemhuis.info> (raw)
In-Reply-To: <543c2e9b-6d82-7ee0-9a1f-e3176aba16e2@amd.com>
On 09.02.23 16:41, Limonciello, Mario wrote:
> On 2/9/2023 09:31, Jason A. Donenfeld wrote:
>> Do not register a hwrng for certain AMD TPMs that are running an old
>> known-buggy revision. Do this by probing the TPM2_PT_MANUFACTURER,
>> TPM2_PT_FIRMWARE_VERSION_1, and TPM2_PT_FIRMWARE_VERSION_2 properties,
>> and failing when an "AMD"-manufactured TPM2 chip is below a threshold.
>>
>> BROKEN BROKEN BROKEN - I just made the version numbers up and haven't
>> tested this because I don't actually have hardware for it. I'm posting
>> this so that Mario can take over its development and submit a v2 himself
>> once he has confirmed the versioning info from inside AMD.
>
> Thanks, happy to do that.
Just a quick note from my side: many many thx to both of you for taking
care of this!
Ciao, Thorsten
next prev parent reply other threads:[~2023-02-11 15:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-09 15:31 [PATCH RFC] tpm: disable hwrng for known-defective AMD RNGs Jason A. Donenfeld
2023-02-09 15:41 ` Limonciello, Mario
2023-02-09 17:26 ` Jason A. Donenfeld
2023-02-11 15:15 ` Linux regression tracking (Thorsten Leemhuis) [this message]
2023-02-10 0:54 ` Jarkko Sakkinen
2023-02-10 1:08 ` Jason A. Donenfeld
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=08063f18-95de-bf2d-4f03-8b72b2eac7c4@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=James.Bottomley@hansenpartnership.com \
--cc=Jason@zx2c4.com \
--cc=jarkko@kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=regressions@lists.linux.dev \
/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.