I wanted a countertop dishwasher. Home depot doesn’t have them in stores, it was online only. I figured it would probably make me make an account in order to check out. I said nah.
sandalbucket
KANAEEEEDDDDAAAAAAAAA!!!
It’s an open source linux graphics driver.
It is very widespread, despite being quite slow, because it works. It ships by default with almost everything, and is the fallback when card-specific drivers fail
Edit: what Max_P said
I have declared war on notifications. My immediate family, two closest friends, and my boss can call me. In no other circumstances will my phone make a noise or vibrate. I will check my texts when I feel like it.
Other than a few exceptions, no apps may show the notification badge either. Discord will show DMs and mentions from one or two servers. Everything else is blocked. My work email may show unread email. I’ve even turned off banners on my work chat app. I don’t think I’ve checked my personal email in months.
All my recurring charges are paperless + autopay. That’s another notification badge I forgot about - I have a budgeting app that can show transactions. I categorize them, make sure their categories are covered, and I’m done.
On the first of the month, I pay rent and set the budgeting app categories. Then I have nothing to worry about, and near-zero distractions. My biggest pain point in life is deciding what to eat for dinner.
This is absolute gold. To the right person, this comment is priceless. Thank you for typing all this out. This is wisdom right here.
Anything exposed to the internet will be found by the scanners. Moving ssh off of port 22 doesn’t do anything except make it less convenient for you to use. The scanners will find it, and when they do, they will try to log in.
(It’s actually pretty easy to write a little script to listen on port 20 (telnet) and collect the default login creds that the worms so kindly share)
The thing that protects you is strong authentication. Turn off password auth entirely, and generate a long keypair. Disable root login entirely.
Most self-hosted software is built by hobbyists with some goal, and rock solid authentication is generally not that goal. You should, if you can, put most things behind some reverse-proxy with a strong auth layer, like Teleport.
You will get lots of advice to hide things behind a vpn. A vpn provides centralized strong authentication. It’s a good idea, but decreases accessibility (which is part of security) - so there’s a value judgement here between the strength of a vpn and your accessibility goals.
Some of my services (ssh, wg, nginx) are open to the internet. Some are behind a reverse proxy. Some require a vpn connection, even within my own house. It depends on who it’s for - just me, technical friends, the world, or my technically-challenged parents trying to type something with a roku remote.
After strong auth, you want to think about software vulnerabilities - and you don’t have to think much, because there’s only one answer: keep your stuff up to date.
All of the above covers the P in PICERL (pick-uh-rel) for Prepare. I stands for Identify, and this is tricky. In an ideal world, you get a real-time notification (on your phone if possible) when any of these things happen:
- Any successful ssh login
- Any successful root login
- If a port starts listening that you didn’t expect
- If the system watching for these things goes down (have two systems that watch each other)
That list could be much longer, but that’s a good start.
After Identification, there’s Contain + Eradicate. In a homelab context, that’s probably a fresh re-install of the OS. Attacker persistence mechanisms are insane - once they’re in, they’re in. Reformat the disk.
R is for recover or remediate depending on who you ask. If you reformatted your disks, it stands for “rebuild”. Combine this with L (lessons learned) to rebuild differently than before.
To close out this essay though, I want to reiterate Strong Auth. If you’ve got strong auth and keep things up to date, a breach should never happen. A lot of people work very hard every day to keep the strong auth strong ;)
For the Nth time, crowdstrike circumvented the testing process
Edit: this is not to say that cs didn’t have to in order to provide their services, nor is this to say that ms didn’t know about the circumvention and/or delegate testing of config files to CS. I’ll take any opportunity to rag on MS, but in this case it is entirely on CS.
Crowdstrike is big, but not that big.
About half of my clients use them; and of those, about a third are halfway through ripping them out in favor of MS defender.
(MS is definitely “that big”)
I want to spin up a separate thread here if that’s okay.
Please give me an example of any EDR solution produced through “public ownership structures”. I don’t think such a thing exists, but I welcome being proven wrong.
Private ownership and investment of capital created Crowdstrike as a profit-seeking venture. It also created MS Defender, SentinelOne, trellix, carbon black, etc. Competition in the marketplace (and there was/is lots of competition) forced these products to be as good as they could, and or self-stratify into pricing tiers. Crowdstrike, being the best (and most expensive) is the most widely-used. Note that not every enterprise requires that level of security, and so while CS is widely used, it is not ubiquitous. This outage could have been significantly worse.
Crowdstrike runs at ring 0, effectively as part of the kernel. Like a device driver. There are no safeguards at that level. Extreme testing and diligence is required, because these are the consequences for getting it wrong. This is entirely on crowdstrike.
Veilidchat mentioned!