![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://sh.itjust.works/pictrs/image/c38fd5ff-821e-45c9-b2ee-957d0321d2e2.webp)
Second-to-worst-case scenario was the best we could do at the time.
Second-to-worst-case scenario was the best we could do at the time.
A lot of teams only made it through the weekend with help from Postmates.
Then they get to suffer the consequences when shit like this happens
Oh, they are.
I’d be surprised if a data center didn’t.
Then you’d be surprised.
More than that: it’s an IT security and infrastructure admin issue. How was this 3rd party software update allowed to go out to so many systems to break them all at once with no one testing it?
Crowdstrike did the same to Linux servers previously.
If you have urgent questions or concerns, consider contacting CrowdStrike support directly.
Something tells me that isn’t going to provide the comfort it was meant to.
Autospill affects Android password programs including keepass2android. Not a flaw in Keepass (which I use) but in Android.
This is why it’s critically important to use a password manager.
Except for people who used 1Password, DashLane, LastPass, Enpass, Keeper, and Keepass2Android.
However to mitigate it as much as possible is what DMARC DNS entries are supposed to help with, by providing assurance that the email was sent by an SMTP server allowed to send email on behalf of the domain.
+DKIM and SPF as long as we’re naming email authentication methods.
Dwarf Fortress no longer counts, huh?