Southwest Airlines Saved From Global IT Outage Thanks To 32-Year-Old Microsoft System

Probably still works if you can find the tape for it.
Recently I interviewed for a position and they panel started asking me about my IT knowledge, which is slim/lean. The center of gravity for the panel asking me the question was the preservation of evidence that is in a digital form.

I clearly responded I don't know so much about IT. After the interview, I realized I could have stated I know much about data preservation and hidden data.

I would have said on a 8" floppy disk a tinky plastic sticker is used to write protect the data. If the disk has a cut on both sides, then data may be written on both sides of the disk. Next I would have stated that is the same for 5 1/4 disks. But for the 3 1/2 disks, a plastic clip that is built into the disk is slid to prevent writing on the disk.

I blew it ...... I could have bamboozled them talking old school floppy disks....
 
Just because the FBI didn't head up the investigation doesn't mean they weren't involved.
  • April 30, 2016: CrowdStrike was contacted by the DNC outside counsel to discuss a suspected breach. This was CrowdStrike’s first involvement in this matter. (p6)
  • May 1-2, 2016: CrowdStrike initiated an investigation into the breach of the DNC network. (p26)
  • June 10-13, 2016: The DNC network remediation took place. (p35)
  • June 13, 2016: CrowdStrike and the DNC outside counsel alerted the FBI that they had identified Russian actors on the DNC network. (p35)
  • June 2016: The FBI requested forensic information, indicators of compromise (pieces of malicious code) that CrowdStrike discovered on the DNC computer network. With DNC permission, CrowdStrike continued to share information from the breach through December 2016, including “digital images” or copies of hard-drives. (p35)
All your references are 404.
Post ignored.
 
Last edited:
The above was cut and pasted from the following link - all links are active. For clarification, I'm in no way trying to validate Crowdstrike, just pointing out they have released information specifically addressing this topic. That said, I have no reason to not believe what is stated in this link either.

https://www.crowdstrike.com/blog/bears-midst-intrusion-democratic-national-committee/
The links only work if you open them directly from within the Crowdstrike.com article. Using the links that you embedded in Post #17 brings up the following error notice.

1721502864234.jpg
 
This is a huge pet peeve of mine.

There are older operating systems that simply work. That's all they need to do.

We engineer a lot of complexity into simple tools that only need to accomplish simple tasks. There is also this not so little thing about the OS version of software which seems to find any little opportunity to track and monetize a human being.

The study I co-developed, the Long-Term Quality Index, is offered for free forever at a site that does not use cookies.

We don't put advertisements online or let any third-parties do anything to our content.

What's the outcome? Super-fast loading times and the average visitor spends over seven minutes there. In Internet terms that's an eternity.
That’s pretty far from the truth.

Nobody has static expectations for airline operations.

Customers want new functionality. Operators want greater efficiency, new features and new capabilities.

United has invested billions of dollars into improved IT architecture to be able to roll out new features and capabilities into its operations and to customers.

Rebooking options, customer connection saving software, flight planning software, baggage tracking and literally hundreds of other new capabilities have been developed over the past several years.

United’s CIO has won awards, outside the airline industry, for her work, including the best app in the business.

That app knows when you land, provides you directions and time to your connecting gate, lets you track your bags, choose seats, rebook flights, connect to WiFi in flight for free messaging, track your flight using flight aware and dozens of other new capabilities.

The airline that stays static for capability, and static in the enabling architecture, is losing.

Like Spirit.

Making things better for customers is how you win in the customer service business. That requires new tech and new tools.

Not a static, limited IT backbone on which to run it all.

An app screen shot from my last flight. Taken in flight.

IMG_3301.webp
 
I started with DOS in 1983 so I know a thing or three about how DOS and Windoze evolved. Windows 98 was a very stable OS but was asked to run on very palty and buggy hardware at the time.
Being on the 98 Beta test team, there was a reason we ended up with 98SE and it wasn't because 98 was very stable. 98 was an evolution of 95 bringing in USB support and DirectX for gaming. ME was the final take on the 32-bit overlay on a 16-bit subsystem (DOS), basically tarting up 98SE, adding the NT5/2K GUI and a handful of buggy features.
It actually had very very few exploitable vulnerabilites.
It had tons of vulnerabilities. Smurf, BackOrifice, PingofDeath, heck, there was a suite of tools packaged with a single GUI that could wreak havoc on 98 computers with net access (didn't even need to be internet, just on the same LAN). We used to have a ball printing to people's printers at Uni that were on 95 or 98, and you could just cancel the Windows network login screen to gain access to the computer.
Win 2K was "for business" but Microsoft panicked when napster and file sharing took off and rushed to replace 98/ME with XP.
Windows 2000 (NT5) was the successor to NT4. Unlike NT4, Microsoft was pushing for more consumer adoption as they were moving everything toward the more secure 32-bit NT kernel and subsystem. However, 2K Pro was more expensive and compatibility with many games was still problematic, so they came out with ME, which had the 2K GUI.

Napster, Limewire, Azureus...etc. P2P wasn't the reason Microsoft came out with XP (which was in development before 2K even went gold). XP cemented the end of DOS-underpinned OS's, an era which Microsoft was keen to get behind it.
98 didn't require remote activation, neither did 2K or ME, but Micro$haft built remote activation into XP.
Which was easily circumventable with corp keys which many of us had memorized (same as for 2K and 98).
XP wasn't ready for general deployment as a consumer OS,
It was actually probably the best Gold OS Microsoft had released and was incredibly stable, which is why it is still in use more widely than either Vista or Windows 8, two successor products. Microsoft was forced to support it far longer than intended (and still provides dedicated security updates for it) because of how ubiquitous it became on embedded and automated systems.
it was from day 1 a trojan-hosting platform and was the reason why spam was able to become an industry (direct-to-mx SMTP spamming through infected / trojanized XP systems). By 2014, after 14 years, XP was finally locked down sufficiently to be somewhat safe to connect to the internet as 98.
That's nonsense. XP was the first Microsoft OS to have an actual firewall, which finally meant that you didn't get instantly pwn3d if you decided to raw dog the Internet. Popular firewall solutions like Atguard (later sold to Norton) and Zone Alarm that we used on 2K could be made to work on XP, but it at least had some manner of protection out of the box, unlike its predecessors.

Open relays (often Exchange, but not always, sendmail, Lotus and many others were also abused) were the primary reason for early widespread mail system abuse/SPAM. It wasn't consumer XP boxes. Orgs (often SMB's, they were likely the biggest culprits) would be running on-prem mail servers that were directly exposed to the internet with no security, and this was prolific. This is why the SPAM systems like SPAMCop went after restricting blocks that weren't designated to be sending that class of traffic.
 
Last edited:
The links only work if you open them directly from within the Crowdstrike.com article. Using the links that you embedded in Post #17 brings up the following error notice.

View attachment 231293
Cool, click on the Crowdstrike link provided and scroll to the relevant section if you want to click the links. Otherwise, I didn’t post specifically for links, just the content the links are embedded in.
 
Being on the 98 Beta test team, there was a reason we ended up with 98SE and it wasn't because 98 was very stable. 98 was an evolution of 95 bringing in USB support and DirectX for gaming. ME was the final take on the 32-bit overlay on a 16-bit subsystem (DOS), basically tarting up 98SE, adding the NT5/2K GUI and a handful of buggy features.

It had tons of vulnerabilities. Smurf, BackOrifice, PingofDeath, heck, there was a suite of tools packaged with a single GUI that could wreak havoc on 98 computers with net access (didn't even need to be internet, just on the same LAN). We used to have a ball printing to people's printers at Uni that were on 95 or 98, and you could just cancel the Windows network login screen to gain access to the computer.

Windows 2000 (NT5) was the successor to NT4. Unlike NT4, Microsoft was pushing for more consumer adoption as they were moving everything toward the more secure 32-bit NT kernel and subsystem. However, 2K Pro was more expensive and compatibility with many games was still problematic, so they came out with ME, which had the 2K GUI.

Napster, Limewire, Azureus...etc. P2P wasn't the reason Microsoft came out with XP (which was in development before 2K even went gold). XP cemented the end of DOS-underpinned OS's, an era which Microsoft was keen to get behind it.

Which was easily circumventable with corp keys which many of us had memorized (same as for 2K and 98).

It was actually probably the best Gold OS Microsoft had released and was incredibly stable, which is why it is still in use more widely than either Vista or Windows 8, two successor products. Microsoft was forced to support it far longer than intended (and still provide dedicated security updates for it) because of how ubiquitous it became on embedded and automated systems.

That's nonsense. XP was the first Microsoft OS to have an actual firewall, which finally meant that you didn't get instantly pwn3d if you decided to raw dog the Internet. Popular firewall solutions like Atguard (later sold to Norton) and Zone Alarm that we used on 2K could be made to work on XP, but it at least had some manner of protection out of the box, unlike its predecessors.

Open relays (often Exchange, but not always, sendmail, Lotus and many others were also abused) were the primary reason for early widespread mail system abuse/SPAM. It wasn't consumer XP boxes. Orgs (often SMB's, they were likely the biggest culprits) would be running on-prem mail servers that were directly exposed to the internet with no security, and this was prolific. This is why the SPAM systems like SPAMCop went after restricting blocks that weren't designated to be sending that class of traffic.
Nicely put, and as I said, we live in a world of revisionist history where everyone longs for the “good old days”, because they’ve rewritten what actually happened, when the truth is those days sucked.
 
Nicely put, and as I said, we live in a world of revisionist history where everyone longs for the “good old days”, because they’ve rewritten what actually happened, when the truth is those days sucked.
Yup. One of the reasons Microsoft was so eager to get away from the 9x OS's was the lack of real memory management and protected memory space. Any app could just take however much RAM it wanted, and while it was supposed to give it back, it wasn't policed/controlled by the kernel, so inevitably you'd run out of RAM and get a hard lock or BSOD if you had a program that had a memory leak or a program could overwrite memory allocated by another program, also triggering a crash or lock, and this wasn't uncommon.

We take this sort of behaviour for granted now ("oh no, Chrome is using 8GB of RAM and my computer is slow" not considering the fact that at least the computer is still running) but this was a HUGE improvement in bringing the NT kernel into the consumer space.
 
Last edited:
That’s pretty far from the truth.

Nobody has static expectations for airline operations.

Customers want new functionality. Operators want greater efficiency, new features and new capabilities.

United has invested billions of dollars into improved IT architecture to be able to roll out new features and capabilities into its operations and to customers.

Rebooking options, customer connection saving software, flight planning software, baggage tracking and literally hundreds of other new capabilities have been developed over the past several years.

United’s CIO has won awards, outside the airline industry, for her work, including the best app in the business.

That app knows when you land, provides you directions and time to your connecting gate, lets you track your bags, choose seats, rebook flights, connect to WiFi in flight for free messaging, track your flight using flight aware and dozens of other new capabilities.

The airline that stays static for capability, and static in the enabling architecture, is losing.

Like Spirit.
SouthWest Airlines is taking a beating in the market place because essentially their computer system can't reserve all the seats on an airplane. Stories are rampant about 20 pre boarders in wheel chairs-then at the destination they are miraculously healed and walk off.
Travelers are sick of it.
Making things better for customers is how you win in the customer service business. That requires new tech and new tools.

Not a static, limited IT backbone on which to run it all.

An app screen shot from my last flight. Taken in flight.

View attachment 231302
So
 
Nicely put, and as I said, we live in a world of revisionist history where everyone longs for the “good old days”, because they’ve rewritten what actually happened, when the truth is those days sucked.

Internet survival time for Windows XP was measured in minutes. It was a joke. When you got your win-XP machine or you just installed XP, and the first time you went on-line to do the first session of Windoze Update, you machine was hacked before the patches were downloaded and installed. Remember those days? No? You don't?

https://forum.beyond3d.com/threads/windows-unprotected-survival-time-is-now-40-minutes.19732/

Posted to various XP newsgroups in April 2014:

When MS stopped supporting Win-98 in July 2006, there was a grand total of 33 security issues that had been identified during it's 7-year lifespan:

=======================
Vulnerability Report: Microsoft Windows 98 Second Edition:

http://secunia.com/advisories/product/13/?task=advisories
(use wayback machine to get that link, it used to work years ago)

Affected By:
33 Secunia advisories
22 Vulnerabilities

Unpatched:
9% (3 of 33 Secunia advisories)

Most Critical Unpatched:

The most severe unpatched Secunia advisory affecting Microsoft Windows 98 Second Edition, with all vendor patches applied, is rated Less critical.
=======================

Now compare that to the most current (and probably very close to the final tally):

Vulnerability Report: Microsoft Windows XP Professional:

========================
http://secunia.com/advisories/product/22/?task=advisories
(again, wayback machine)

Affected By:
446 Secunia advisories
668 Vulnerabilities

Unpatched:
10% (44 of 446 Secunia advisories)

Most Critical Unpatched: The most severe unpatched Secunia advisory affecting Microsoft Windows XP professional, with all vendor patches applied, is rated Highly critical.
========================
 
Last edited:
Internet survival time for Windows XP was measured in minutes. It was a joke. When you got your win-XP machine or you just installed XP, and the first time you went on-line to do the first session of Windoze Update, you machine was hacked before the patches were downloaded and installed. Remember those days? No? You don't?

https://forum.beyond3d.com/threads/windows-unprotected-survival-time-is-now-40-minutes.19732/

Posted to various XP newsgroups in April 2014:

When MS stopped supporting Win-98 in July 2006, there was a grand total of 33 security issues that had been identified during it's 7-year lifespan:

=======================
Vulnerability Report: Microsoft Windows 98 Second Edition:

http://secunia.com/advisories/product/13/?task=advisories
(use wayback machine to get that link, it used to work years ago)

Affected By:
33 Secunia advisories
22 Vulnerabilities

Unpatched:
9% (3 of 33 Secunia advisories)

Most Critical Unpatched:

The most severe unpatched Secunia advisory affecting Microsoft Windows 98 Second Edition, with all vendor patches applied, is rated Less critical.
=======================

Now compare that to the most current (and probably very close to the final tally):

Vulnerability Report: Microsoft Windows XP Professional:

========================
http://secunia.com/advisories/product/22/?task=advisories
(again, wayback machine)

Affected By:
446 Secunia advisories
668 Vulnerabilities

Unpatched:
10% (44 of 446 Secunia advisories)

Most Critical Unpatched: The most severe unpatched Secunia advisory affecting Microsoft Windows XP professional, with all vendor patches applied, is rated Highly critical.
========================
You're writing style and tone are confusing and I can't determine if you agree with me or not. Anyway, yeah XP sucked.
 
Being on the 98 Beta test team, there was a reason we ended up with 98SE and it wasn't because 98 was very stable. 98 was an evolution of 95 bringing in USB support and DirectX for gaming. ME was the final take on the 32-bit overlay on a 16-bit subsystem (DOS), basically tarting up 98SE, adding the NT5/2K GUI and a handful of buggy features.

It had tons of vulnerabilities. Smurf, BackOrifice, PingofDeath, heck, there was a suite of tools packaged with a single GUI that could wreak havoc on 98 computers with net access (didn't even need to be internet, just on the same LAN). We used to have a ball printing to people's printers at Uni that were on 95 or 98, and you could just cancel the Windows network login screen to gain access to the computer.

Windows 2000 (NT5) was the successor to NT4. Unlike NT4, Microsoft was pushing for more consumer adoption as they were moving everything toward the more secure 32-bit NT kernel and subsystem. However, 2K Pro was more expensive and compatibility with many games was still problematic, so they came out with ME, which had the 2K GUI.

Napster, Limewire, Azureus...etc. P2P wasn't the reason Microsoft came out with XP (which was in development before 2K even went gold). XP cemented the end of DOS-underpinned OS's, an era which Microsoft was keen to get behind it.

Which was easily circumventable with corp keys which many of us had memorized (same as for 2K and 98).

It was actually probably the best Gold OS Microsoft had released and was incredibly stable, which is why it is still in use more widely than either Vista or Windows 8, two successor products. Microsoft was forced to support it far longer than intended (and still provides dedicated security updates for it) because of how ubiquitous it became on embedded and automated systems.

That's nonsense. XP was the first Microsoft OS to have an actual firewall, which finally meant that you didn't get instantly pwn3d if you decided to raw dog the Internet. Popular firewall solutions like Atguard (later sold to Norton) and Zone Alarm that we used on 2K could be made to work on XP, but it at least had some manner of protection out of the box, unlike its predecessors.

Open relays (often Exchange, but not always, sendmail, Lotus and many others were also abused) were the primary reason for early widespread mail system abuse/SPAM. It wasn't consumer XP boxes. Orgs (often SMB's, they were likely the biggest culprits) would be running on-prem mail servers that were directly exposed to the internet with no security, and this was prolific. This is why the SPAM systems like SPAMCop went after restricting blocks that weren't designated to be sending that class of traffic.
Nice write up.

I really liked 2000. At the time I was in the military in the Communications Command and we were authorized to make pre-authorized copies and hand them out to anyone that wanted one. We also made copies of, I think Norton, to hand out. With the popularity of email at the time, the government was concerned about security and wanted the troops to have the best security that was available at the time.

I also liked XP. It was the last Microsoft product I ever used after moving on to something else.

DOS, 95 and 98 were OK but 2000 was a huge improvement.
 
Agree, seems like some in here are not understanding, not a Microsoft issue. Faulty software update from a 3rd party that the individual companies subscribed to, a third party service and the reason the ones that did not subscribe are untouched by the failure.
It’s a corporate IT issue if you do not vet , test and release an update yourself.

Companies I work at always seems to delay updates by a week or so to ensure they don’t destroy their working infrastructure.
 
It’s a corporate IT issue if you do not vet , test and release an update yourself.

Companies I work at always seems to delay updates by a week or so to ensure they don’t destroy their working infrastructure.
That is thought provoking. How many individuals (private citizens) have automatic updates, by default for their computer/ smartphone. On my MSFT OS notebook, I know MSFT wants to turn back on automatic updates, am incessantly. Very easy to have automatic updates, often quite challenging to turn off automatic updates and keep it off.
 
Software is freakin' expensive. Companies pay so much for such low performance. That's my opinion.
Yes companies like Microsoft only, Dell absolutely agree. Garbage. They only recommend their product suite which may not be best of breed so you end up with so so solution.

Other software produce pretty amazing software if they can pick the best of underlying products(AWS, Azure, Google) with strong resilient architecture aligned to well customer needs.
 
Last edited:
Internet survival time for Windows XP was measured in minutes. It was a joke. When you got your win-XP machine or you just installed XP, and the first time you went on-line to do the first session of Windoze Update, you machine was hacked before the patches were downloaded and installed. Remember those days? No? You don't?

https://forum.beyond3d.com/threads/windows-unprotected-survival-time-is-now-40-minutes.19732/
That's what I was making reference to as "raw dogging" the internet. You'll notice the caveat there (emphasis mine):
2005 thread said:
According to the latest data at the SANS Internet Storm Center, the average time it takes for an unprotected PC running Microsoft Windows (i.e., firewall off and missing critical security patches) to be compromised after being plugged into the Internet has more than doubled since September 2004. Trouble is, that time gap still isn't that large: An unguarded Windows computer can expect to be hacked within little more than 40 minutes of going online.

This was during a period of time where the vast majority of people didn't have home routers. Computers were plugged directly into the internet, so you had a public IP and were exposed to every potential cyber threat out there. Home gateways (well, home WiFi gateways in most instances) are now ubiquitous, but that was not the case during the late stage 98/ME/2000 days or the early Windows XP days.
Posted to various XP newsgroups in April 2014:

When MS stopped supporting Win-98 in July 2006, there was a grand total of 33 security issues that had been identified during it's 7-year lifespan:

=======================
Vulnerability Report: Microsoft Windows 98 Second Edition:

http://secunia.com/advisories/product/13/?task=advisories
(use wayback machine to get that link, it used to work years ago)

Affected By:
33 Secunia advisories
22 Vulnerabilities

Unpatched:
9% (3 of 33 Secunia advisories)

Most Critical Unpatched:

The most severe unpatched Secunia advisory affecting Microsoft Windows 98 Second Edition, with all vendor patches applied, is rated Less critical.
=======================
The problem with using this list is that CVE's stopped being released for Windows 98 around 2006 because Microsoft stopped releasing updates for it and abandoned it.
Microsoft leaves Windows 98 to the hackers | CSO Online

CVE's weren't tracked like they are today back in the 90's and early 2000's, so you are going to find large differences in numbers reported. For example, this site shows 86 vulnerabilities for 98:
Microsoft Windows 98 : Security vulnerabilities, CVEs (cvedetails.com)

Microsoft's own list of security vulnerabilities can be downloaded from here. Note that Windows 98 is not included in anything later than 2006 due to the end of Extended support.
Security Bulletins | Microsoft Learn

Same can be seen on the official CVE tracker:
NVD - Results (nist.gov)

This thread includes a list of updates, final list is 90 in 2008, with 82 superceded:
The complete list of hotfixes & updates for Windows 98se - Windows 9x/ME - MSFN

For an operating system with a support life of ~8 years and no Server version.
Now compare that to the most current (and probably very close to the final tally):

Vulnerability Report: Microsoft Windows XP Professional:

========================
http://secunia.com/advisories/product/22/?task=advisories
(again, wayback machine)

Affected By:
446 Secunia advisories
668 Vulnerabilities

Unpatched:
10% (44 of 446 Secunia advisories)

Most Critical Unpatched: The most severe unpatched Secunia advisory affecting Microsoft Windows XP professional, with all vendor patches applied, is rated Highly critical.
========================
I doubt we are close to the final tally, since CVE's affecting XP are still being tracked. Here's the current official list:
NVD - Results (nist.gov)

649 CVE's, but of course many, if not most of them not specific to XP itself.
For example the most recent is an SQL injection from 2023 (CVE-2023-31702)
2nd most recent from 2020, affecting GE Volusion medical software from 2020 (CVE-2020-36549)

The most recent specific to the OS appears to be this one from 2017:
NVD - CVE-2017-0176 (nist.gov)

And Microsoft was still releasing updates for XP in 2017, 16 years after the product went gold:
Download Security Update for Windows XP Service Pack 3 (KB4012583) from Official Microsoft Download Center
Microsoft Update Catalog

This was driven by Military, healthcare and embedded use of the product, something that was never a problem with 98:
The US Navy is paying Microsoft $9.1 million for continued Windows XP support | Windows Central
Why the military can’t quit Windows XP. (slate.com)
 
Back
Top Bottom