Linux users face a Microsoft Secure Boot headache - here's the painkiller

[Condobloke]

Linux users face a Microsoft Secure Boot headache - here's the painkiller

Secure Boot has always been a nuisance for Linux users, but now that Microsoft's 2011 certificate authorities are expiring, it's become a real pain.

www.zdnet.com

Secure Boot has always been a nuisance for Linux users, but now that Microsoft's 2011 certificate authorities are expiring, it's become a real pain.
Read the article It is not a sign to assume panic stations.
There is a paragraph at the bottom of the article which says:
For you, the simplest test is also the most practical:

• Download a current ISO from your distro and write it to a USB stick.
• On a machine with Secure Boot enabled, and the firmware freshly updated, try booting with the USB stick.
• If it works cleanly, your combination of firmware keys and distro signing is OK, and you're good to go.

Do this test once now, so you know what the new normal looks like. If a future image fails to boot with Secure Boot enabled, you'll be able to tell whether the regression is in the firmware (keys not updated), the distro's image, or a nasty interaction between the two.

(Note: the firmware for my asrock board has no firmware update available. it made no difference to my passing the above test)