Thanks for the report, Masum. I'm not sure if this is actually a bug against fwupd or just that fwupd is the tool that reported the change.
And it's entirely possible that this is the correct outcome. If the TPM device changes on a system, it's suddenly a very different system. Hopefully someone more familiar with what's being done here will have some input; I suspect this is all "working as intended". Thanks ** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/2047374 Title: TPM PCR0 recontruction fails on Pluton fTPM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/2047374/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
