On Wed, Jan 15, 2020 at 6:05 AM pmkellly(a)frontier.com
<pmkellly(a)frontier.com> wrote:
On 1/13/20 2:35 PM, Chris Murphy wrote:
In regard to the TPM2 issue:
> Did you read the bug I cited?
>
https://bugzilla.redhat.com/show_bug.cgi?id=1769215
>
Yes, this bug seems to be the exact problem I have. It doesn't matter if
it's turned on or off.
> It's supposed to be fixed now. If you're seeing something different
> than what's reported in that bug, then it needs a new bug filed. If
> it's the same thing, you need to let them know what version you're
> using and that it's not fixed.
>
I have not implemented the fix. I am reluctant to do such things on user
machines. I followed your example and removed the tpm2-abrmd packages
from those machines. I'll monitor for the released fix I doubt that
reinstalling it will be useful. The complaint in the journal is that
those machines have TPM1.2 instead of TMP2. Right now I'm thinking I
won't bother reinstalling it. Unless you know of a reason that it would
be good to do so. I may have to budget for some newer machines.
Good firmware would require vendor signed firmware updates. I have no
idea how that's actually verified, and if some implementations
leverage the TPM for that, and what minimum version is required. But
I'd say even if your machines aren't supported by fwupd for firmware
updates, you can still apply them however the manufacturer normally
provides, and that is recommended.
Otherwise, right now, I don't think we're leveraging the TPM for anything else.
--
Chris Murphy