News for hackers. Stuff that matters.
Re:The Dangers of Microsoft Pluton by SSLy on Tuesday July 26, 2022 @07:36AM (#32236915)
>As of January 2021 deleting SecureBoot keys and installing your own keys (for example by using KeyTool) will brick the device. This is a problem that is similar to one which has been reported on some other Lenovo laptops [0] and is likely due to a faulty firmware. If the device is stuck in a boot loop after replacing the SecureBoot keys, the only way to repair it is by replacing the mainboard of the device.

[0] https://forums.lenovo.com/t5/ThinkPad-X-Series-Laptops/BIOS-...

From https://wiki.archlinux.org/title/Lenovo_ThinkPad_T14/T14s_(I...

Re:The Dangers of Microsoft Pluton by userbinator on Tuesday July 26, 2022 @09:40AM (#32238129)
Does reflashing the BIOS EEPROM (via hardware clip) work? Or have they "secured" that out of the question too?
Re:The Dangers of Microsoft Pluton by trelane on Tuesday July 26, 2022 @01:11PM (#32241001)
I'd be surprised if that's not one of the bits of firmware that's checked on boot. So yeah, probably not possible, and not possible to downgrade.
Re:The Dangers of Microsoft Pluton by monocasa on Tuesday July 26, 2022 @01:15PM (#32241035)
The goal is that it's secured as well; the bios image itself is measured into the TPM and pluton as part of secure boot.