144 points

the good news is that it does make windows more secure. you cant hack something that has crashed.

permalink
report
reply
76 points

permalink
report
parent
reply
44 points

Remember guys, it took about a decade for Solar Winds to discover somebody had root access to everybody that used their software, another decade for somebody outside Solar Winds to discover it and tell everybody, and half a decade with nobody claiming to have solved the issue up to now.

So when you believe that your computer with an EDS is safe just because you can’t use it, think again.

permalink
report
parent
reply
5 points

EDS?

permalink
report
parent
reply
1 point

It’s an oops.

It should be IDS.

permalink
report
parent
reply
25 points

The most secure computer is the one not running any software. That’s why I recommend Crowdstrike.

permalink
report
parent
reply
21 points

Reminds me of a local cyber security firm, which declares war on a group of hackers. The CEO went on television to “double dog dare” the hackers to hack their servers and claim their firewalls are impenetrable.

Well you can guess the results, within 48 hours, their servers went down one after another. And when shit about to hit the fan, they literally turned off all of their servers for days. They hired a 3rd party IT firm to patch their security, then the CEO declared victory in a local newspaper.

permalink
report
parent
reply
13 points

Similar thing happened to the idiot CEO of Lifelock that used to advertise his actual social security number everywhere.

permalink
report
parent
reply
9 points

I used to work at Equifax. LifeLock was the subject of many corporate trainings.

permalink
report
parent
reply
7 points

A smarter person would have used a fake SSN then claimed success when it never worked

permalink
report
parent
reply
6 points

And the hackers name? 4chan

permalink
report
parent
reply
104 points

The fact that random companies like Crowdstrike have kernel drivers in millions of computers they they ship remotely is a security risk in and of itself. We’re lucky crowdstrike just shipped a bug that crashes computers, other companies could have shipped a lot worse.

permalink
report
reply
47 points

other companies could have shipped a lot worse.

other companies governments could have shipped a lot worse.

FTFY

permalink
report
parent
reply
22 points
*

other companies governments could have may have already shipped a lot worse.

FTFY (high five!)

permalink
report
parent
reply
7 points

I’d swap may out for probably TBH.

permalink
report
parent
reply
4 points

I HATE UEFI I HATE UEFI I HATE UEFI

permalink
report
parent
reply
66 points

I’d laugh if this wasn’t affecting me directly.

permalink
report
reply
26 points

I can laugh either for or at you, if you want.

I’ll pour one out for the frontliners.

permalink
report
parent
reply
3 points

I laugh and it does/did(over now) affect me. Bwahaha. Im getting work done and nobody can interrupt with email.

permalink
report
parent
reply
3 points

All I’ve noticed is that a lot of internet related things in my work are much faster today.

The schadenfreude could only be sweeter if my company used CrowdStrike on all the Windows systems. Then I really would have had a very peaceful focused day.

permalink
report
parent
reply
41 points

I really don’t want to be the guy responsible for this fuck up

permalink
report
reply
37 points

For a company this big it would also have to have gotten past a code review and QA team, right? … right? …

permalink
report
parent
reply
18 points

Of course, of course. This is how these things are always done.

permalink
report
parent
reply
11 points

I like how they kept on pushing the update for hours

permalink
report
parent
reply
10 points
*

And who pushes out production updates on a Friday!

permalink
report
parent
reply
6 points

We do.

“If something goes down over the weekend, fewer people see it” - my leadership team.

I guess Asia can report the problem on Sunday and I’ll get a nastygram and fix it that afternoon.

permalink
report
parent
reply
5 points

“Security”

permalink
report
parent
reply
4 points

Code review, QA team, hours of being baked on an internal test network, incremental exponential roll out to the world, starting slow so that any problems can be immediately rolled back. If they didn’t have those basics, they have no business being a tech company, let alone a security company who puts out windows drivers.

permalink
report
parent
reply
19 points

Yeah, something this big is absolutely not one engineer’s fault. Even if that engineer maliciously pushed an update, it’s not their fault — it was a complete failure of the organization, and one person having the ability to wreck havoc like this is the failure.

And I actually have some amount of hope that, in this case, it is being recognized as such.

permalink
report
parent
reply
3 points

I agree but they will still blame it all on that one guy.

permalink
report
parent
reply
9 points

No they won’t, not if they’re in the slightest bit competent.

Blameless post-mortem culture is very common at big IT organizations. For a fuck-up this size, there are going to be dozens of problems identified, from bad QA processes, to bad code review processes, to bad documentation, to bad corner cases in tools.

There will probably be some guy (or gal) who pushed the button, but unless what that person did was utterly reckless (like pushing an update while high or drunk, or pushing a change then turning off her phone and going dark, or whatever) the person who pushed the button will probably be a legend to their peers. Even if they made a big mistake, if they followed standard procedures while doing it, almost everyone will recognize they’re not at fault, they just got to be the unlucky person who pushed the button this time.

permalink
report
parent
reply
12 points

This is an industry wide issue. This is just the first symptom.

permalink
report
parent
reply
6 points

What we need is to stop the blind trust

permalink
report
parent
reply
5 points

Yeah and that means they won’t nail some poor schmuck to the wall over this?

permalink
report
parent
reply
6 points

He’ll just get fired, apply somewhere else, and they’ll only know the dates he worked at CrowdStrike.

If anybody cared, they would have switched away from M$ by now.

permalink
report
parent
reply
40 points

Also: don’t trust your employees to boot into safe mode.
Trust a 3rd party to freely install system level files at any time.

I knew how to fix the computers at work today in the morning, but we couldn’t get through to the help desk to get the bit locker codes for each computer until near the end of the day.

permalink
report
reply
14 points
*

Also: don’t trust your employees to boot into safe mode. Trust a 3rd party to freely install system level files at any time.

Exactly. This is exactly the problem, and unless people wisen up the software security problem is only going to get worse. Companies and Governments need to rethink how they approach security entirely. This is a preview of what is to come, its only going to get worse and more damaging from here, and none of the vendors care.

permalink
report
parent
reply
3 points
*

Companies and Governments need to rethink how they approach security entirely. This is a preview of what is to come, its only going to get worse and more damaging from here, and none of the vendors care.

It is easy one for goverments. Ban security through obscurity. As well proprietary security software.

Moonbutt’s moonbuck))) Have I seen you somewhere?

permalink
report
parent
reply
2 points
*

Ban security through obscurity. As well proprietary security software.

The government likes proprietary software. They are never going to ban it.

permalink
report
parent
reply

linuxmemes

!linuxmemes@lemmy.world

Create post

Hint: :q!


Sister communities:

Community rules (click to expand)

1. Follow the site-wide rules
2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack members of the community for any reason.
  • Leave remarks of “peasantry” to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn. Even if you watch it on a Linux machine.
4. No recent reposts
  • Everybody uses Arch btw, can’t quit Vim, and wants to interject for a moment. You can stop now.

Please report posts and comments that break these rules!

Community stats

  • 6.6K

    Monthly active users

  • 1.3K

    Posts

  • 69K

    Comments