NHacker Next
- new
- past
- show
- ask
- show
- jobs
- submit
login
▲Windows and Linux users: The deadline to update Secure Boot keys is nearself.__VINEXT_RSC_CHUNKS__=self.__VINEXT_RSC_CHUNKS__||[];self.__VINEXT_RSC_CHUNKS__.push("2:I[\"aadde9aaef29\",[],\"default\",1]\n3:I[\"6e873226e03b\",[],\"Children\",1]\n5:I[\"bc2946a341c8\",[],\"LayoutSegmentProvider\",1]\n6:I[\"6e873226e03b\",[],\"Slot\",1]\n7:I[\"3506b3d116f7\",[],\"ErrorBoundary\",1]\n8:I[\"a9bbde40cf2d\",[],\"default\",1]\n9:I[\"3506b3d116f7\",[],\"NotFoundBoundary\",1]\na:\"$Sreact.suspense\"\n:HL[\"/assets/index-BLEkI_5r.css\",\"style\"]\n")> (arstechnica.com)
Rendered at 09:39:26 GMT+0000 (Coordinated Universal Time) with Cloudflare Workers.
Where to look? Is fwupd involved?
https://github.com/pbatard/Mosby
With UEFI systems all kinds of malware were enabled to take "root" on your motherboard after that.
Zeroing your drive won't help you now.
Plus with Microsoft SecureBoot finally proving without a doubt to be quite a false-sense-of-security system, some people there just aren't as advanced as the average person used to be. Or were more predatory on users than ever and ended up enabling some real bad actors to do even worse. Without considering or not caring about the collateral damage of their own "solution" including a hardware time-bomb "to boot".