this post was submitted on 07 Nov 2024
569 points (98.1% liked)

Technology

59300 readers
4556 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 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 94 points 6 days ago (2 children)

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

[–] [email protected] 118 points 6 days ago (1 children)

They labelled an OS version upgrade as a security update.

[–] [email protected] 27 points 6 days ago (1 children)

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

[–] [email protected] 41 points 6 days ago (1 children)

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.

[–] [email protected] 12 points 6 days ago (2 children)

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

[–] [email protected] 11 points 6 days ago (1 children)

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.

[–] [email protected] 0 points 5 days ago* (last edited 3 days ago)

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

[–] [email protected] 11 points 6 days ago* (last edited 6 days 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.

[–] [email protected] 7 points 6 days ago (1 children)

Wrong.

Microsoft labelled the update as a security update

[–] [email protected] -3 points 5 days ago* (last edited 3 days ago) (1 children)

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

[–] [email protected] 7 points 5 days ago* (last edited 5 days ago) (1 children)

Read the fucking article.

The patch id couldnt be any clearer.

[–] [email protected] -3 points 5 days ago* (last edited 3 days 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?