Exactly, the blame here is entirely on Crowdstrike. they could just as easily have made similar mistake in an update for the Linux agent that would crash the system and bring down half the planet.
I will say, the problem MIGHT have been easier to fix or work around on the Linux systems.
Not only is "Googling" one of my most important job skills, now that I'm doing professional services, my entire job basically consist of "Learn product ${FOO} faster than the customer's employees can." Which of course primarily consists of knowing what to search for, how to find it, and how to interpret and use what I find.
So I've been in situations where I was stopped at a red light, and emergency vehicles were coming and I was waved by a policeman to cross the intersection against the red light to clear the way.
So what, is a self driving car going to just sit there and keep the intersection blocked?
Upon re-reading, it looks like there is two paths, but both require two steps?
The first part, proposing an amendment:
An amendment may be proposed by a two-thirds vote of both Houses of Congress, OR, if two-thirds of the States request one, by a convention called for that purpose.
Then the second part, ratifying the amendment:
The amendment must then be ratified by three-fourths of the State legislatures, OR three-fourths of conventions called in each State for ratification.
Just because our previous civil war involved a relatively simple geographical separation, doesn't mean it's necessary for a civil war.
The only thing you need is two (or more) sides with opposing beliefs about how the country should run and who should run it, and that said beliefs are strong enough that people are willing to use violence to ensure that their side wins.
Once again you seem to be calling for not bothering with any security effort of there's even a remote chance of some other vulnerability happening.
The whole point of security is that it's always a multi-layered thing. Nobody sane is pretending that encrypting web traffic with HTTPS is a panacea that's going to solve all your data security needs. But it is sure as hell a million times better than having all of your data transmitted in the clear, with absolutely no assurance that you're are talking to the system you think you're talking to, or that the data hasn't been tampered with in transit.
And don't pretend https is a huge burden. It's dead simple to get SSL/TLS certs, and the additional load of encrypting and decrypting the traffic is barely even a rounding error on modern CPUs.
I have the same issue (TRIPLE NAT'd! One of which is the CGNAT). Unfortunately I have external family that accesses from media boxes/TVs so those won't work for me.
Thankfully I was able to get a small VPS server for $2/mo and set up some reverse tunnels with auto-ssh. Seems to be working fairly well so far.
All that said, I longingly look forward to the future when I don't have to worry about NAT.
Because up until Broadcom bought them, it was a good product with a ton of useful features, endless supported integrations with 3rd party software and hardware, relatively easy to learn/use, with good support, all at reasonable and flexible price points depending on your needs.
Of course Broadcom has now thrown all of that into the toilet...
Yeah pretty much. I mean I do the best I can (and I do have resources to look to for help).