556
you are viewing a single comment's thread
view the rest of the comments
[-] MonkderVierte@lemmy.ml 93 points 1 month ago

Misleading title. It was installed by a third-party updater, Heimdall, but MS labeled a Windows 11 update wrong.

[-] superkret@feddit.org 114 points 1 month ago

They labelled an OS version upgrade as a security update.

[-] dditty@lemm.ee 28 points 1 month ago

Yet another reason to not do auto-updates in an enterprise environment for mission-critical services.

[-] superkret@feddit.org 40 points 1 month ago

In an enterprise environment, you rely on a service that tracks CVEs, analyzes which ones apply to your environment, and prioritizes security critical updates.
The issue here is that one of these services installed a release upgrade because Microsoft mislabelled it as security update.

[-] NocturnalEngineer@lemmy.world 14 points 1 month ago

Should still be doing phased rollouts of any patches, and where possible, implementing them on pre-prod first.

[-] mosiacmango@lemm.ee 11 points 1 month ago* (last edited 1 month ago)

Pre-prod is ideal, but a pipe dream for many. Lots of folks barely get prod.

We still stagger patching so things like this only wipe some of the critical infrastructure, but that still causes needless issues.

[-] SomeGuy69@lemmy.world 11 points 1 month ago

For security updates in critical infrastructure, no. You want that right away, in best case instant. You can't risk a zero day being used to kill people.

[-] Appoxo@lemmy.dbzer0.com 2 points 1 month ago* (last edited 1 month ago)

Even security updates can be uncritical or supercritical. Consult the patch notes or get burned lol

[-] Wooki@lemmy.world 9 points 1 month ago

Wrong.

Microsoft labelled the update as a security update

[-] Appoxo@lemmy.dbzer0.com 1 points 1 month ago* (last edited 1 month ago)

Do you know that's not a mistake and done fully malicously knowing that? Please give me your source.

[-] Wooki@lemmy.world 7 points 1 month ago* (last edited 1 month ago)

Read the fucking article.

The patch id couldnt be any clearer.

[-] Appoxo@lemmy.dbzer0.com 1 points 1 month ago* (last edited 1 month ago)

And you make absolutely no error?

Besides that:
Should MS have caught the errorenous ID (assuming it truly was errourneous and not knowingly falsely labeled)? Absolutely. Should the patch management team blindly release all updates that MS releases? No?

this post was submitted on 07 Nov 2024
556 points (100.0% liked)

Technology

60083 readers
2798 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each another!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. Check for duplicates before posting, duplicates may be removed

Approved Bots


founded 2 years ago
MODERATORS