News for hackers. Stuff that matters.
Re:Windows Bluescreen and Boot Loops (update: caused by a Cr... by zik on Friday July 19, 2024 @04:38AM (#41003608)
But no damage actually ended up happening with the xz utils exploit. It didn't even get released because someone picked it up pre-release.

Every system gets attacked, but I think your point shows that even with state-level attacks Linux handles it better than other platforms.

Re:Windows Bluescreen and Boot Loops (update: caused by a Cr... by AdeptusAquinas on Friday July 19, 2024 @04:45AM (#41003690)
Hmm? It was released for two plus months? 5.6.0 and 5.6.1

I'd also say this wasn't a good example of 'linux handling it better': usually when a mess like this occurs on windows all the corps get a quiet tap on the shoulder that they need to immediately patch when MS releases it, then a few days later it hits the news. In XZ's case, the backdoor was published before the team knew about it, huge mess.

Re:Windows Bluescreen and Boot Loops (update: caused by a Cr... by adrian17 on Friday July 19, 2024 @06:25AM (#41004561)
You’re right that it went noticed for a long time, just one clarification

> all the corps get a quiet tap on the shoulder that they need to immediately patch when MS releases it, then a few days later it hits the news

AFAIK, distros were notified and released a patched version of xz like a week before it hit the news, so at least a lot of machines received it via automatic updates.

Re:Windows Bluescreen and Boot Loops (update: caused by a Cr... by AdeptusAquinas on Friday July 19, 2024 @07:03AM (#41004899)
Depends which news you're talking about. MS guy who discovered it found it March 29th, published to oss. It was in infosec news same day as redhat, others pushed out critical advisories. Patch didn't come til a day or two later.
Re:Windows Bluescreen and Boot Loops (update: caused by a Cr... by zik on Friday July 19, 2024 @07:15AM (#41005022)
It didn't go out in any distros.