this post was submitted on 21 Jul 2024
582 points (93.0% liked)

Technology

59669 readers
3109 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
 

Southwest Airlines, the fourth largest airline in the US, is seemingly unaffected by the problematic CrowdStrike update that caused millions of computers to BSoD (Blue Screen of Death) because it used Windows 3.1. The CrowdStrike issue disrupted operations globally after a faulty update caused newer computers to freeze and stop working, with many prominent institutions, including airports and almost all US airlines, including United, Delta, and American Airlines, needing to stop flights.

Windows 3.1, launched in 1992, is likely not getting any updates. So, when CrowdStrike pushed the faulty update to all its customers, Southwest wasn’t affected (because it didn’t receive an update to begin with).

The airlines affected by the CrowdStrike update had to ground their fleets because many of their background systems refused to operate. These systems could include pilot and fleet scheduling, maintenance records, ticketing, etc. Thankfully, the lousy update did not affect aircraft systems, ensuring that everything airborne remained safe and were always in control of their pilots.

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

Or, for your consideration, could it perhaps be because they don't use crowdstrike?

[–] [email protected] 74 points 4 months ago (2 children)

Yeah, what? 3.1 not getting updates has nothing to do with this. Software developed for 3.1 can still be updated. This article is just silly.

[–] [email protected] 12 points 4 months ago

It isn't even a Windows update, but a software update.

[–] [email protected] 59 points 4 months ago (1 children)

My Linux servers weren't affected either. I think it's because of Windows 3.1

[–] [email protected] 35 points 4 months ago (3 children)

My wife shared this with me yesterday, but I didn’t see it:

A joke tweet with an attached image of a smart refrigerator. The refrigerator displays a blue screen of death. The tweet reads “I can’t even open my fridge.” Another tweet is replying to it, taking it seriously and indicating they do not embrace smart technology.

Somebunny is gonna learn those things aren’t windows-based today!

[–] [email protected] 15 points 4 months ago (2 children)

Just yesterday I had that exact "Tech enthusiast vs tech worker" meme play out. I wanted a timer to control the electrical outlet for an aquarium bubbler. Saleswoman really wanted to sell me this "smart" controller with an app that can program the outlet.

Me:"What happens when the app stops working?"

(saleswoman is frantically flipping the box over for answers)

Her:"...maybe...it keeps the existing timer?"

[–] [email protected] 13 points 4 months ago (1 children)

I've got about six smart plugs that all stopped working because of lack of support. I am no longer interested in smart plugs.

[–] [email protected] 9 points 4 months ago

Shelly makes devices that are compatible with ESPHome and Tasmota, solving this problem.

[–] [email protected] 9 points 4 months ago (3 children)

For only way more time and money, you can buy a zigbee smart plug and a vendor agnostic zigbee hub flashed with FOSS, or you can buy a esp-based board, wire it up with a relay, and flash it with something like esphome.

Sure, it’s way more money and hours of work (cumulatively), but it won’t lose support!

load more comments (3 replies)
load more comments (2 replies)
[–] [email protected] 14 points 4 months ago

I feel like every article out there is missing this and keeps blaming Windows Update vs an update pushed to a specific piece of software by a third-party developer. I get end-users not understanding how things work but tech writers should be more knowledgeable about the subject they write about for a living.

load more comments (1 replies)
[–] [email protected] 138 points 4 months ago (3 children)

Best feature windows 3.1 has:

... it doesn't pop up message telling you to upgrade to windows 11.

[–] [email protected] 59 points 4 months ago (1 children)

or add shitty AI tools without asking.

or constntly nag you to use their cloud storage

[–] [email protected] 15 points 4 months ago

Plus all them decks for solitaire!!!

[–] [email protected] 24 points 4 months ago (3 children)

My windows 10 PC is telling me I don't qualify for a free Windows 11 update, so I've got that going for me.

load more comments (3 replies)
[–] [email protected] 15 points 4 months ago

Shhh don't give microsoft any ideas

[–] [email protected] 90 points 4 months ago (5 children)

Windows 3.1 didn’t have the BSOD. It just froze. I remember with Windows NT 4, when we first got the BSOD, being so grateful that Microsoft decided to actually tell us that our computer wasn’t going to recover from the error. Otherwise, we’d just be sitting there, waiting, hoping it would unfreeze itself.

It never did

[–] [email protected] 23 points 4 months ago* (last edited 4 months ago)
[–] [email protected] 18 points 4 months ago (1 children)

Windows 3.1 did have a BSOD. It wasn't always fatal, you could try to hit enter to go back to Windows, but most of the time it wasn't really recoverable, Windows often wouldn't work right afterwards.

I ran into them all the time in 3.11 on our 486 which had some faulty RAM (the BSOD would even be scrambled). If we could get back to Windows after that, it'd just be in a zombie state where moving the mouse around would paint stuff over whatever was left on screen, and wouldn't respond to clicks or keypresses.

Fun times.

load more comments (1 replies)
[–] [email protected] 8 points 4 months ago* (last edited 4 months ago) (1 children)

Are you sure? I remember a long time ago being able to trigger a BSOD by opening Windows Calculator and dividing any number by 0. And I'm pretty sure that was 3.1 or 3.11.

In fact, I remember being able to change the color of the BSOD.

[–] [email protected] 10 points 4 months ago* (last edited 4 months ago) (1 children)

As another user mentioned, the BSOD first came in Windows NT 3.51.

But it definitely wasn’t in Windows 3.1 or Windows 3.11

load more comments (1 replies)
load more comments (2 replies)
[–] [email protected] 79 points 4 months ago (7 children)

The fact that they’re running 3.1 is not something to be proud of. They’re probably extremely vulnerable to any other attack.

load more comments (7 replies)
[–] [email protected] 77 points 4 months ago (6 children)

This... Doesn't make me feel any better about flying Southwest

load more comments (6 replies)
[–] [email protected] 59 points 4 months ago (8 children)

This is the "can't get a Word Document macro virus because I use the Corel WordPerfect Document type" kind of energy.

load more comments (8 replies)
[–] [email protected] 54 points 4 months ago (2 children)

One X user suggested that the company switch to Windows XP—it’s also no longer updated, and it can run Windows 3.1 applications via compatibility mode.

Maybe that was a joke, but if anything that would reduce their security. Windows 3.1 and 95 are old enough that they can't even run most stuff from the last two and a half decades, which probably protects them. XP is just new enough, and plenty old enough, to be very risky.

[–] [email protected] 27 points 4 months ago (1 children)

Reminds me of an episode of Ghost in the Shell where a hacker in a hyper-advanced cyberised society was using floppy disks as a storage medium because they were so slow.

[–] [email protected] 28 points 4 months ago

One of the background details I liked in Ghost in the Shell was how the high-end data analysts and programmers employed by the government did their work using cybernetic hands whose fingers could separate into dozens of smaller fingers to let them operate keyboards extremely quickly. They didn't use direct cybernetic links because that was a security vulnerability for their brains.

load more comments (1 replies)
[–] [email protected] 43 points 4 months ago (3 children)

Holy crap, they are serious. I though I was on [email protected] for a minute. I sure hope none of those computers are connected to the internet. There's a massive number of vulnerabilities in windows 3.1 and windows 95.

[–] [email protected] 21 points 4 months ago (2 children)

Windows 3.1 doesn't even come with a TCP/IP stack. It's actually pretty safe.

[–] [email protected] 17 points 4 months ago (1 children)

As long as that's the exact version they're using. Windows for workgroups 3.11 has networking.

load more comments (1 replies)
load more comments (1 replies)
load more comments (2 replies)
[–] BingBong 31 points 4 months ago (1 children)

Is this actually confirmed anywhere though? I keep seeing it repeated and the only 'source' is a ?xeet? .

[–] [email protected] 8 points 4 months ago

Same, I'm pretty sure it's not true.

[–] [email protected] 23 points 4 months ago

This is both awesome and frightening for many reasons

[–] [email protected] 23 points 4 months ago (1 children)

Maybe don’t pay a company to install a rootkit on your critical infrastructure?

[–] [email protected] 23 points 4 months ago

Just open up your critical infrastructure to the public Internet and you’ll get rootkits for free.

[–] [email protected] 23 points 4 months ago (1 children)

I’m inclined to believe this post, claiming this article is BS https://mastodon.social/@jplebreton/112825798853315264

load more comments (1 replies)
[–] [email protected] 16 points 4 months ago (2 children)

If they still use Windows 3.1 and it works, then I do have to wonder about the rest of their security setup.

load more comments (2 replies)
[–] [email protected] 16 points 4 months ago (2 children)

So...Battlestar Galactica scenario?

load more comments (2 replies)
[–] [email protected] 15 points 4 months ago (1 children)

Hang on, if you're using CrowdStrike but not getting the updates, then why are you using it at all?

[–] 5redie8 29 points 4 months ago

Because none of these journalists have a basic understanding of what actually happened lol

[–] [email protected] 15 points 4 months ago (3 children)

Windows 3.1? You fancy kids, and your modern operating systems! What's wrong with Windows 1.0???

load more comments (3 replies)
[–] [email protected] 15 points 4 months ago (1 children)

And they can play JezzBall.

load more comments (1 replies)
[–] [email protected] 15 points 4 months ago

That makes fuckall sense.

Windows 3.1 not being updated by Microsoft has nothing to do with Crowdstrike rolling out an update to their Falcon Sensor software including a file with 42kB of zeroes.

On Windows 3.1 you probably can't run Falcon Sensor, so in that way it could be related. But it seems way more likely that Southwest Airlines simply didn't use Falcon Sensor on their normal Windows 10 or whatever clients.

There are probably competitors to Crowdstrike, at least some companies would be customers to one of them.

[–] [email protected] 12 points 4 months ago

I thought everyone already switched to 3.11

load more comments
view more: next ›