Does fwupd check DB before DBX update? Is there a warning for revoked files present before DBX is applied? #8376
Replies: 2 comments
Yup, we do that now if you use fwupdmgr or fwupdtool to deploy the dbx update. We've had that for some time. If you're using either the original dbxtool (or the fwupd-provided backwards compatibility version) you can do anything you like with no checks. e.g. google for "Blocked executable in the ESP, ensure grub and shim are up to date" to see all the real people that hit this. :) |
|
Thanks! I think I did the |
Uh oh!
There was an error while loading. Please reload this page.
Describe the question
In the light of latest Microsoft updates on Jan 14th 2025, it looks like the revocation of
Microsoft Windows Production PCA (Product Certificate Authority) 2011certificate is included in the update. This means any bootloader or driver signed under that certificate will no longer work. Can fwupd tool verify that there is no revoked binary or firmware present before applying DBX? When I test this on a Linux install with a vulnerable driver store din EFI filesystem, I did not get a warning. May be my version is too old?I can see I was Abel to update the DBX to bock the latest Howyar vulnerability CVE-2024-7344 or VU#529659
fwupd version information
All reactions