𝓢𝓮𝓮𝓙𝓪𝔂𝓔𝓶𝓶 to Linux • 3 months agoCritical vulnerability affecting most Linux distros allows for bootkitsarstechnica.comexternal-linkmessage-square28fedilinkarrow-up1172arrow-down124 cross-posted to: security
arrow-up1148arrow-down1external-linkCritical vulnerability affecting most Linux distros allows for bootkitsarstechnica.com𝓢𝓮𝓮𝓙𝓪𝔂𝓔𝓶𝓶 to Linux • 3 months agomessage-square28fedilink cross-posted to: security
minus-square@dsemy@lemm.eelinkfedilinkEnglish63•3 months agoThis is a vulnerability in shim, which is a UEFI “bootloader” used by distros mainly to allow booting with the “stock” (Microsoft) secure boot keys. If you don’t use secure boot or don’t use shim (likely if you use your own keys), this doesn’t affect you at all. In any case this “critical vulnerability” mainly affects machines relying on shim which also boot over unencrypted HTTP.
minus-squarealliswell33 linkfedilink8•edit-23 months agoWould this affect systems booting to the refind bootloader without secure boot? Sorry for the ignorance just trying to figure out if I should be changing my system for this news.
minus-square@Jordan_Ulink5•3 months agoNo. This is a vulnerability which allows bypassing secure boot protections. You have already manually bypassed those protections by disabling secure boot.
This is a vulnerability in shim, which is a UEFI “bootloader” used by distros mainly to allow booting with the “stock” (Microsoft) secure boot keys.
If you don’t use secure boot or don’t use shim (likely if you use your own keys), this doesn’t affect you at all.
In any case this “critical vulnerability” mainly affects machines relying on shim which also boot over unencrypted HTTP.
Would this affect systems booting to the refind bootloader without secure boot? Sorry for the ignorance just trying to figure out if I should be changing my system for this news.
No
No.
This is a vulnerability which allows bypassing secure boot protections. You have already manually bypassed those protections by disabling secure boot.