Chewy to Linux@lemmy.ml • 1 year agoJust about every Windows and Linux device vulnerable to new LogoFAIL firmware attackarstechnica.comexternal-linkmessage-square105fedilinkarrow-up1368arrow-down114cross-posted to: technology@hexbear.netcybersecurity@lemmy.mlnews@lemmy.linuxuserspace.showtechnology@lemmy.worldtecnologia@feddit.clhackernews@derp.foohackernews@lemmy.smeargle.fanstechnology@lemmy.zipprivacy@lemmy.ml
arrow-up1354arrow-down1external-linkJust about every Windows and Linux device vulnerable to new LogoFAIL firmware attackarstechnica.comChewy to Linux@lemmy.ml • 1 year agomessage-square105fedilinkcross-posted to: technology@hexbear.netcybersecurity@lemmy.mlnews@lemmy.linuxuserspace.showtechnology@lemmy.worldtecnologia@feddit.clhackernews@derp.foohackernews@lemmy.smeargle.fanstechnology@lemmy.zipprivacy@lemmy.ml
minus-square@lazylion_ca@lemmy.calinkfedilink15•1 year agoIf you have access to replace the logo file, you probably have access to enable it as well.
minus-square@fl42v@lemmy.mllinkfedilink6•1 year agoNot necessarily, I guess. They’re talking about a firmware upgrade of sorts, and, at least on the machines I own(ed), performing it didn’t reset user settings (which disabling the logo is)
If you have access to replace the logo file, you probably have access to enable it as well.
Not necessarily, I guess. They’re talking about a firmware upgrade of sorts, and, at least on the machines I own(ed), performing it didn’t reset user settings (which disabling the logo is)