IIRC those were the non-eBPF versions of the sensor.
IIRC those were the non-eBPF versions of the sensor.
It has a little bit to do with the OS. Windows does not have the same sandboxing capability for modules that Linux provides. The fact that the sensor needs to run in ring 0 is a problem, and eBPF at least mitigates much of the issue in Linux. But I think you meant that CrowdStrike is by no means blameless, and I agree - they have a long history of shitty implementations, and rightly deserve to be the focus of our anger.
Since FF 6 and 7 have already been mentioned, I’m going to give a honorable mention to Shining Force.
Proud of Canada for making it this far! No shame in losing against the current champions.
I don’t get why people are down voting this. Your approach is a perfectly acceptable blueprint for reducing meat consumption. Getting upset at you because you haven’t fully embraced veganism is letting perfect become the enemy of good enough.
When I was younger and more naïve, I used to think a case was useless. I kept my phones in my pocket most of the time, and didn’t feel particularly clumsy or reckless. Then I got a phone that happened to have a glass back, and it broke not because I fumbled it, but because it slid out of my pocket onto time floor while I was sitting down. Glass backs on phones are bullshit.
So TCP ACK is the backwash?
They mistook them for crayons.
Good fucking riddance to that massive waste of oxygen.
rapid mitosis
As in you are seeing multiple boot entries? It’s likely one entry per kernel version that you have installed. It doesn’t happen often these days any more, but in some situations it’s handy to be able to revert to a previous kernel if for example third party modules break.
Remember it’s the Financial Post. Gotta take things they say with a heaping pile of salt.
Not sure about erasing all of it, but it is (or was) certainly possible to delete enough of it to brick a motherboard https://www.phoronix.com/news/UEFI-rm-root-directory
I don’t know where you got the idea that I’m arguing that old versions don’t get new vulnerabilities. I’m saying that just because a CVE exists it does not necessarily make a system immediately vulnerable, because many CVEs rely on theoretical scenarios or specific attack vectors that are not exploitable in a hardened system or that have limited impact.
The fact that you think it’s not possible means that you’re not familiar with CVSS scores, which every CVE includes and which are widely used in regulated fields.
And if you think that always updating to the latest version keeps you safe then you’ve forgotten about the recent xz backdoor.
Just because it has a CVE number doesn’t mean it’s exploitable. Of the 800 CVEs, which ones are in the KEV catalogue? What are the attack vectors? What mitigations are available?
You did a recursive chown or chmod, didn’t you.
To be fair though, the chance that every Lemmy instance goes down at the same time is so much lower than Reddit going down. Sure, my instance might be unavailable, but I’d be able to hop onto the next one and continue.
Brian Kernighan. Got the chance to have lunch with him!
And increase social spending. Of those who can be reformed, they’ll only do so if there’s a support network.