Hi Beelink CS-Yvette
Thank you for the update.
One thing I’m still confused about is the T112/T113 timeline.
In the previous GTi14 thread here:
GTi14 — AMI Test Key (PKFAIL) and old Microsoft SecureBoot certs
The issue was reported on T112, and Beelink later provided a new BIOS privately. The user confirmed that this BIOS added the new 2023 Secure Boot keys.
However, T113 was released publicly on April 4, while the T112 fix was provided later, on May 21. More importantly, the official T113 ROM still contains the AMI Test PK / “DO NOT TRUST - AMI Test PK”.
Could you please clarify whether the Secure Boot fix provided for T112 was ever incorporated into T113? If not, why was T113 released without the fix?
I’m asking because this appears to be more than just a fwupd reporting issue — the AMI Test PK is actually present in the T113 firmware itself.
Hopefully R&D can take this into consideration when preparing the new BIOS. In particular, the final BIOS should ensure that the AMI Test PK is removed from the factory Secure Boot configuration and that resetting the Secure Boot keys to factory defaults does not restore it again.
