view the rest of the comments
Star Wars Memes
Hello there. Somehow, Star Wars memes have returned. It's not a trap, this is where the fun begins.
==========
Other universes to visit:
Separatist systems:
Oh hey some real SW content for a change (perhaps):
!starwarstelevision@lemmy.world
==========
IMPORTANT
Please do not post the "good friend" or similar copypasta
==========
Our galactic citizens have requested more specific rules, so here are a few.
The general idea is, if you're looking here for rules, you're probably someone who doesn't need to have them spelled out. You're fine. But anyway:
-
This is a community for Star Wars memes. This means typically screenshots of Star Wars media with some text or context that's meant to be funny and/or thoughtful. All SW media is welcome: movies, games, comic books, fanart... Other kinds of content, like video links or meta memes (about this community, or Lemmy), are fine as well, just keep it on topic.
-
We are all friends here, and love (sometimes love to hate) Star Wars. Be nice to each other.
-
As fans of fictional media, we can be passionate. If you very strongly disagree with something or someone, take a deep breath before reacting. Anger leads to the dark side!
-
Everything in Star Wars has happened a long time ago, in a galaxy far away, and it's a rich universe of millions of words and millions of years of history. So current Earthly matters really shouldn't concern us here. In other words, leave politics, philosophies and convictions behind the door. This applies even if it's about something related to Star Wars.
-
Original content is preferred. Reposts are fine, just please limit to a maximum of 3 per day, per citizen. It is recommended, but not required, to mark original memes as (OC) and reposts as (repost).
-
Local mods are the Jedi council. They may take actions that are necessary to maintain peace and stability of the Republic, even beyond the rules outlined here. Follow their guidance.
-
Regular rules of the Lemmy.world instance apply.
..... But it's not malware like Solar winds became. It was just a botched update.
I hope they learn from this and implement update stages or groups so you don't blow away an entire org again.
Sounds like malware to me!
It's not the users computer, it's the employers. The user has no rights on it.
Depends on how their user is configured. Admins have plenty of rights 🤓
so work elsewhere that doesn't use it. You have no rights to a device you do not own.
I still have human rights, as well as rights to eg.: privacy. Also it's not like they put "we use CrowdStrike" in their job offerings you know, so you saying to just "work elsewhere" reads whiny. And petty.
I agree, but not on a device that is not owned or managed by you. Now, if your employer demanded you install it on your personal PC as a condition of employment then that is a completely separate issue
Is intended to allow c2 traffic to control to machine
Tomato potato
I wiped my computer last night because of that shitty virus. Good luck IT teams out there! lol
You were supposed to delete \windows\system32\drivers\crowdstrike\C-00000291-*.sys, not all of \windows \system32. I know the buttons are right next to each other and all, but come on…
:-)
I assumed I did something wrong. I initially blamed explorerpatcher. Made sense (at the time) to get it fixed before I had to work Friday morning
Now it doesn't even have the stuff my company installed! Woops
The worst bit was once I finally called IT (~10pm, was gonna leave a message or something) they had a recorded message saying they were aware of the BSOD issue. Facepalms were indeed had
I want to say I wish they'd sent out some kind of email asap, but I can't really say I wouldnt have tried to fix it myself. Safe mode wasn't working!! Literally never seen that happen. Oh well, lesson learned
Any third party remotely deploying kernel-level spyware is malware. We as an industry shouldn't accept this kind of behavior.
Is it really spyware if the device owner installs it deliberately? After all this application is not run on home or personal machines. It only runs in corporate environments where you do not own the equipment you use.
It become malicious when you start demanding IT departments to install insecure, untested kernel drivers. Crowdstrike did not own any of the millions of devices they just killed today.
Malicious requires intent. I have massive doubts CS wanted to deploy a Kernel driver full of NULL values to their clients. more likely a human error happened as part of a larger automated process.
It rendered millions of machines unbootable