"t's obvious that the IT world has to come up with something better."
And that receives downvotes? No wonder the IT world is in a mess.
40471 publicly visible posts • joined 16 Jun 2014
"That's a good suggestion, but that's not Microsoft's job."
If Microsoft sign the driver in order to gain that access they do have a job to do which is to require it to be able to roll back and do so. Microsoft are a gatekeeper here. If they say that in order to gain access a third party has to meet quality requirements then that third party has to meet those requirements or stay outside.
The only basis for a regulator to quibble with that would be if Microsoft gave itself a free pass not to meet those requirements itself.
"There's no such thing as a last known good configuration if something updates itself outside of the normal Windows process."
If it updates itself it can revert itself to its last known good configuration if it has maintained a copy of that. If it can't then either the kernel should then fail it or, if it isn't designed to do that, it goesn't get the signature to allow it into the kernel at all.
"The CrowdStrike driver that processes and handles these updates is not very resilient"
And there's the real problem. Anything with that privilege needs to be very resilient.
Does the driver require signing by Microsoft to be allowed this access? If so then Microsoft need to exert some strict QA before doing so. And, yes, I recognise that there might be a slight problem/irony (choose according to personal preference) there.
I can't remember seeing any but the new initramfs being rebuilt. It would negate the whole point of keeping the old kernels available.
And single user here (Devuan) wants a root password to bring up a root shell for single user or a Ctrl-D to continue normal boot. What are you running?
"Like the way my Linux Mint session is instantly terminated if I set a font to 96pt in Libre Office or Abiword and zoom in once?"
You keep saying that. I just entered A at 98pt Liberation Serif in LO Writer at zoom 100% and zoomed right up to 400% with no adverse effect. This is Devuan/KDE.
Maybe it's systemd? [Ducks]
More seriously, is it a specific font, every font or just some fonts?
The nearest traffic lights to me - please bork them. Everyone agrees traffic flows much better when they're out of action
I don't think I'd want anything from any of McDonald's machines but from what I hear perhaps it would fix them.
Sewage systems, yes might be a problem.
But would any embedded systems old enough to have a 32-bit time_t still be working by then?
There are these old-fashioned things called IT departments. As this seems to be a product aimed at big corporates there's a fair chance their customers still have them. Not guaranteed these days, but a fair chance. The IT department does the test and makes the decision on behalf of its users - and does the roll-out. I suppose they could still roll out something they know will bork all the workstations on the grounds that it will keep out ransomware but at least it becomes a deliberate choice.
There are also perfectly good reasons why you don't want systems to fall back to dead, especially when they're collectively running a large part of the world's infrastructure including health care systems.
There are no two ways about it: this cannot be argued into having been an acceptable situation.
"you're only paying for the right to use this; we don't guarantee anything; if something bad happens, tough sh*t."
Given the impact of this lawyers are going to be looking vary carefully for ways round any such clauses. For instance if this bypasses any controls the customer might wish to make and pushes (or pulls) files in automatically then that might be caught by some provision such as the UK Computer Misuse Act.
I'm old and cynical so am (a) inclined to ask for evidence of that "only" 8.5 million and (b) inclined, on the basis of evidence of the fact that the file crashing their own S/W, that they released both the file and, previously, the S/W that uses it without adequate testing.
Presumably the independent inspection, assuming it's independent and an inspection, will pick up the phone problem in due course. If, as implied, report it in your own organisation with a paper trail to cover yourself when the inspection fails the lift. Alternatively report it to HSE and/or the fire service anonymously.
"Queue management to minimise waiting time, especially in taller buildings."
It still doesn't require a regular connection to the outside world. Even if it occasionally needs an external connection for servicing then just connect externally. And don't use a desktop operating system with all the tranklements that come with a desktop operating system.
With the ultimately greatest respect imaginable, people often make decisions collectively, not individually. A collection of individuals is called a company.
What's more, they may make them by reasoning to meet widely (i.e. more than just the company) accepted criteria. The reasoning might be impeccable. The criteria, however widely accepted may be wrong.
"I want a government inquiry into how some third party American company has the ability to hobble NHS services, and UK airports."
But we know that.
1. They all depend on computers
2. Windows has become the standard operating system because nobody ever got sacked for buying Windows in the same way that "nobody ever got fired for buying IBM".
3. Windows has a virus problem
4 Crowdstrike is one of very few AV products being bought by corporates (probably similar reasoning to 2.
5. Windows, Crowdstrike and any other products which are operationally essential and have a virtual monopoly become a single point of failure
Now where, in that chain, are you going to find any specific individuals you can finger as being responsible as being culpable for buying industry standard products.
Yes, it's a bad situation but what is needed from such an enquiry isn't scapegoating, it's a recommended policy to be acted upon (the second half of that is usually the sticking point) to escape from the monocultures.
"If you cannot code defensively to ensure third party services don't take down your product when they fail, you have no place as a software engineer or a software company."
Likewise if you can't code defensively to ensure your product isn't taken down by your own badly formatted data file.
"perhaps believing that it was better to update them quickly to address new threats rather than delay their release due to testing"
And this file that was so urgently required as to have to be released without testing can, as a workaround, be simply deleted without waiting for a replacement.
I took a look at FlightRadar yesterday afternoon. Traffic was a bit light but still reasonably busy. One thing that struck me when I looked was the track on one of the planes coming into Manchester. It had executed a peculiar loop around Hyde which is where they normally line up for the runway and a following plane had executed a loop a bit further back, neither in the usual holding locations. Clearly something had temporarily held things back. Whether or not it was Cloudstrike I don't know but I've not seen that one before.
The issue here is worse than that. It wasn't the kernel module itself that was replaced, it was a data file which triggered a bug that had been there all along. There was no good version to roll back to. It was entirely the responsibility of the kernel module or whatever it was to handle the bad data file.