OK, I had taken it the other way, I thought it was something like this. I'm not familiar with these questions.
In case of problem (unable to boot), the workaround is to disable Secure Boot in the BIOS. But in your case, this shouldn't be necessary.
Why did you find the message disturbing? Does it really look like an alert?
Since your system is up to date (especially shim-signed), there should be no problem. By the way, have you already rebooted since the dbx update?The Unified Extensible Firmware Interface (UEFI) Forum provides Revocation List files that you can use to update the Secure Boot Forbidden Signature Database (dbx). This database contains the signatures of revoked binaries and certificates which must not be used if Secure Boot is enabled.
In case of problem (unable to boot), the workaround is to disable Secure Boot in the BIOS. But in your case, this shouldn't be necessary.
Why did you find the message disturbing? Does it really look like an alert?
Statistics: Posted by fabien — 2024-10-14 21:50 — Replies 3 — Views 97