this post was submitted on 19 Jul 2024
831 points (98.6% liked)

Technology

59192 readers
2513 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
 

…according to a Twitter post by the Chief Informational Security Officer of Grand Canyon Education.

So, does anyone else find it odd that the file that caused everything CrowdStrike to freak out, C-00000291-
00000000-00000032.sys was 42KB of blank/null values, while the replacement file C-00000291-00000000-
00000.033.sys was 35KB and looked like a normal, if not obfuscated sys/.conf file?

Also, apparently CrowdStrike had at least 5 hours to work on the problem between the time it was discovered and the time it was fixed.

top 50 comments
sorted by: hot top controversial new old
[–] [email protected] 6 points 3 months ago (1 children)

I wonder how many governments and companies will take this as a lesson on why brittle systems suck. My guess is most of them won't... It's popular to rely on very large third party services, which makes this type of incident inevitable.

[–] [email protected] 2 points 3 months ago

oh they'll take it as a lesson all right, up until they get the quote to fix it suddenly the downtime becomes non-issue as long as it "doesn't happen again"

[–] [email protected] 16 points 3 months ago (2 children)

I'm not a dev, but don't they have like a/b updates or at least test their updates in a sandbox before releasing them?

[–] [email protected] 18 points 3 months ago (1 children)

It could have been the release process itself that was bugged. The actual update that was supposed to go out was tested and worked, then the upload was corrupted/failed. They need to add tests on the actual released version instead of a local copy.

[–] [email protected] 0 points 3 months ago

Could also be that the Windows versions they tested on weren't as problematic as the updated drivers around the time they released.

[–] [email protected] 6 points 3 months ago

one would think. apparently the world is their sandbox.

load more comments
view more: next ›