The paper was about the increased likelihood of frog homosexuality.
The paper was about the increased likelihood of frog homosexuality.
*folds phone in half*
That’s two batteries for the price of one.
CPD classic, I still remember when Lori and them decided to raise the bridges downtown to trap protestors during the George Floyd protests. Then they played disperse messages and hit the protestors at the pinch points. Chicago is a great city but CPD is pretty icky, they even have a blacksite.
He works at the CIA
Bruh, I’ve used Linux for over 10 years. I run Arch on my laptop and have a homelab powered by Proxmox, Debian, and OPNSense. I don’t run any AV in my lab but do follow other security practices.
At work it’s a different story. Products like CrowdStrike also collect logs, scan for vulnerabilities, provide graphing and dashboarding capabilities, provide integrations into ticketing platforms for investigation and remediation by security teams, and more. AV is often required because Windows users can upload infected files to Linux-run SMB shares. Products like CrowdStrike often satisfy requirements set by cybersecurity insurance.
This is not simping, this is not Linux vs Windows. You just clearly have no experience in the enterprise Linux space and business security requirements.
Ah, was a bit off. The update disregarded update controls per reddit and I must have misunderstood what exactly the channel update did. I know for the sensors you can set how closely you want to track current releases but I guess the driver update is not considered under those rules. I use CrowdStrike in my day to day but not from the administrative side, sorry for the misinformation. Thanks for the details Gestrid.
CrowdStrike does more than anti-virus and yes enterprise Linux installations need a lot of security controls that average Linux users don’t need.
Something similar did happen on Linux clients with CrowdStrike installed not too long ago lol
It’s because this got pushed as a virus definition update and not a client update bypassing even customer staging rules that should prevent issues like this. Makes it a little more understandable because you’d want to be protected against current threats. But, yeah should still hit testing first if possible.
Nah, CS sent out a virus definition update that included a driver file that was fucked and caused a boot loop. Because it was a virus definition it bypassed staging rules set by customers. It’s 100% on CS unless we want to talk about how Windows architectural choices on how it handles loading improperly formatted kernel level drivers. CS also caused issues on Linux not too long ago.
Good thing about the setup and self updating router is you should have a VPN/(head/tail)scale connection enabled to it so you can still use the smart plug (plugged into the UPS) or send the WoL packet. Or PiKVM. Or if your breaker box is outside ask your neighbor to flip some switches until it comes back to life and come back to an online server and a fridge full of spoiled food.
Smart plug or WOL packet from router go BRRRRR
Yes, Si… System Administrator.
Kinda feel like they’re burying the lede on the whole Hitler shitstache situation. That seems worse than any toilet bowl and brush licking.
Invoke-Command -Sick-Burn $user
Write-Output "Nice"
Fellow humans should I finish the bird muscle with a saccharine concoction, an overfermented grape extract concoction, or a ground plant concoction from the geographic region of Carolina? I know us fellow humans frequently debate the proper and just pairing of concoction and flesh.
☝️🤓aaS