Chewy to Linux@lemmy.ml • 1 year agoJust about every Windows and Linux device vulnerable to new LogoFAIL firmware attackarstechnica.comexternal-linkmessage-square104fedilinkarrow-up1368arrow-down114cross-posted to: cybersecurity@lemmy.mlnews@lemmy.linuxuserspace.showtechnology@lemmy.worldhackernews@derp.footechnology@lemmy.zip
arrow-up1354arrow-down1external-linkJust about every Windows and Linux device vulnerable to new LogoFAIL firmware attackarstechnica.comChewy to Linux@lemmy.ml • 1 year agomessage-square104fedilinkcross-posted to: cybersecurity@lemmy.mlnews@lemmy.linuxuserspace.showtechnology@lemmy.worldhackernews@derp.footechnology@lemmy.zip
minus-square@Bitrot@lemmy.sdf.orglinkfedilinkEnglish18•edit-21 year agoThis is worse than many, since it persists across reinstalls and even potentially drive swaps, and fools systems such as secure boot.
minus-square@wmassingham@lemmy.worldlinkfedilink3•1 year agoIf it’s only on the ESP, it won’t persist across reinstalls, and definitely not drive swaps. But I do see mentions of attacking via firmware capsule. If that works, then yes, that will persist.
minus-square@Bitrot@lemmy.sdf.orglinkfedilinkEnglish3•1 year agoESP is usually not cleared on a reinstall unless somebody takes the extra step to do so. Since each OS has its own directory within the ESP their installers don’t push it. I was mostly referring to modification in firmware though.
This is worse than many, since it persists across reinstalls and even potentially drive swaps, and fools systems such as secure boot.
If it’s only on the ESP, it won’t persist across reinstalls, and definitely not drive swaps.
But I do see mentions of attacking via firmware capsule. If that works, then yes, that will persist.
ESP is usually not cleared on a reinstall unless somebody takes the extra step to do so. Since each OS has its own directory within the ESP their installers don’t push it. I was mostly referring to modification in firmware though.