Earlier quoted context omitted.
I've had trouble nailing down if thats the case from searching around online. And if thats true - thats absolutely on Crowdstrike. And that behavior should disqualify it from being used on critical systems. I imagine this incident will cause a lot of teams to consider just what can happen automatically on their systems.
[flagged]
Why the CrowdStrike bug hit banks hard
161–170 of 250 posts
Re: Why the CrowdStrike bug hit banks hard
#162Earlier quoted context omitted.
> You can't provide a guarantee to the end-user of pre-vetted safety when the application is downloading and executing arbitrary code from a third-party source. So a web browser can't be trusted or certified, ever. Unless JavaScript is disabled?
JS lives in a sandbox, that will require a bug to escape. Plugins are out of sandbox and random plugins should be disabled if security is a concern.
Sandboxing is such a way to attempt to enforce a guarantee (modulo sandbox bugs, of course). Since crexs aren't entirely in the sandbox, vetting and signoff is supposed to provide the added assurance of security the sandbox can't provide. And those assurances are hollow when the vetted crex is running arbitrary code from a third-party source.
Re: Why the CrowdStrike bug hit banks hard
#163The takeaway from this article seems to be: buy crowdstrike shares, because major corps are unable to make any changes, and will continue to pay licensing fees for this "service" for the foreseeable future.
The lawsuits alone are going to be eyewatering. But sure, buy those shares.
A lot of lawsuits are going to be thrown out, I think.
Re: Why the CrowdStrike bug hit banks hard
#164Earlier quoted context omitted.
[flagged]
You're living in a different reality. I can't fathom how anybody could legitimately make that claim. Even if you're defining "critical system" as "critical to humans" and not "critical to the business", then sure, you can say "Airlines aren't critical" and for most passengers, yeah, you're probably right. Most industries aren't critical, so businesses being ground to a halt doesn't matter for the consumers. But 911 s…
Re: Why the CrowdStrike bug hit banks hard
#165Earlier quoted context omitted.
Probably not. A competent government could install temporary rationing for the most essential goods such as food. It happened through the the whole of the 1917—1920 Russian revolution, with four or five kinds of paper money being circulated around, and the urban population managed through it only if barely. That government was much less competent than the US government is today.
I mean, millions still starved during the revolution, even with the American Relief Administration feeding 10% of the country.
Re: Why the CrowdStrike bug hit banks hard
#166Earlier quoted context omitted.
> There is no reason a leading operating system company should be allowed to also be a word processing, video conferencing, and music-selling company. If I write a new OS how will you force the "word processing, video conferencing, and music-selling" companies to write code for it? If they don't write the above my OS is worthless, but if my OS fails in the market anyway they just wasted a lot of money. This is why OS…
You work deals for early access to your OS, and work to make your OS backwards compatible. Nobody wants to try to be selling consumer software that is optimized for the out of date and unsupported version of the OS.
Re: Why the CrowdStrike bug hit banks hard
#167Earlier quoted context omitted.
If you don't do it, someone else will. Unless the OS is locked down to the point that even its owner cannot do that. Actually, this is something I like about Operational Technology, you run into a lot of doodads where the elevation process requires turning a physical key, and the device's main functionality is disabled while it is in service mode. Ofc the doodad has to be engineered to operate reliably, perpetually,…
I have said for 20 years now that Microsoft Word should have a check on startup, if the current user is administrator it should put up a message that administrators are not allowed to use a Word Process, login as someone else. This one change would solve a lot of problems. Even on home machines where no user has a password, having to do something special to get into administrator mode will stop several attacks just b…
This would just result in more UAC prompts and thus annoyed users who get taught to click on "Allow" whenever a dialog pops up.
Re: Why the CrowdStrike bug hit banks hard
#168I'm still amazed how the blame shifted from Microsoft to CrowdStrike. Yes, CrowdStrike update caused that -- but applications fail all the time. It was Microsoft's oversight to put it on Windows critical path. And banks/airlines etc were hit hard because their _Windows_ didn't boot, not because of an application crash on a perfectly working Windows.
This is a valid opinion and I don't know why you were downvoted (well other than the hacker news bubble mindset (or mindless-set). How is Microsoft not to blame, it's their product? We wouldn't blame a Toyota supplier for a failure in a car, but we somehow segment that in the software world?
Do you think Crowdstrike is a Microsoft product?
Re: Why the CrowdStrike bug hit banks hard
#169Earlier quoted context omitted.
I think anti-virus should be part of the core os. This does kill all third party vendors - good riddance to most of them, sorry if there is one that isn't evil (I'm not aware of it)
Once the AV vendors exist, killing them, especially by Microsoft, is clearly anticompetitive. If you could prevail on a government to decide that, maybe it could work. One thing I see, is that AV has a component of maintaining a DB of signatures of bad things. This does not seem at all the job of the core os. Would the Debian team maintain such a DB?
Re: Why the CrowdStrike bug hit banks hard
#170Earlier quoted context omitted.
...you want Microsoft to forbid you from running certain kinds of programs on your own machine, even if you really, really insist on it, do I understand you correctly?
More like: "...you want Microsoft to forbid you from running certain kinds of programs (with gaping security holes / processes) on your own machine" YES
The problem is that you're assuming you can prove a program doesn't having security holes and bad processes.