• 0 Posts
  • 163 Comments
Joined 1 year ago
cake
Cake day: June 21st, 2023

help-circle
  • There are a lot of misunderstandings about what happened. First, the ‘update’ was to a data file used by the crowdstrike kernel components (specifically ‘falcon’.) while this file has a ‘.sys’ name, it is not a driver, it provides threat definition data. It is read by the falcon driver(s), not loaded as an executable.

    Microsoft doesn’t update this file, crowdstrike user mode services do that, and they do that very frequently as part of their real-time threat detection and mitigation.

    The updates are essential. There is no opportunity for IT to manage or test these updates other than blocking them via external firewalls.

    The falcon kernel components apparently do not protect against a corrupted data file, or the corruption in this case evaded that protection. This is such an obvious vulnerability that i am leaning toward a deliberate manipulation of the data file to exploit a discovered vulnerability in their handling of a malformed data file. I have no evidence for that other than resilience against malformed data input is very basic software engineering and crowdstrike is a very sophisticated system.

    I’m more interested in how the file got corrupted before distribution.


  • You’ve doctored your first two points to avoid the fact that widespread corruption and crumbling infrastructure are in fact a feature of the USA. That said, obviously we are not a ‘third world’ country, nor a ‘developing or under-developed’ country. We are, instead in our own special category of fucked. We have an absolutely giant economy, but as we have decided politically to disinvest in all of our public sectors, either by privatization or under-funding, we are rapidly becoming dysfunctional. Add to that the huge global reclaiming of surplus value from workers wages to plutocrats profits, and we are, as is obvious, in a political crisis shared by the rest of the neoliberal democracies.















  • markr@lemmy.worldtohomeassistant@lemmy.worldHA redundancy options
    link
    fedilink
    English
    arrow-up
    6
    arrow-down
    1
    ·
    9 months ago

    I run HA as a container in a vm. I back HA data up nightly and the compose script for running HA is archived on github. If the vm dies there is another vm that can bring it back up. If the host dies (I have a pool of xenserver (xcp-ng) hosts, so it would be a major domestic disaster if they all croaked) I have a fallback to run HA on docker on wsl. If the house burns down all the scripts are on GitHub and the backups get sent to Azure monthly. I think I’m covered.




  • Dred Scott was still in effect in 1860. The federal government was not involved AT ALL in enforcement of slaver’s ‘property rights’ in non-slave states, that enforcement was up to the states, and was generally done by bounty hunters. The election of Lincoln, with the almost certain consequence that Kansas would be admitted as a free state, was the proximate cause of South Carolina’s secession. Slavery was obviously the critical factor, regardless of the enforcement or non-enforcement of Scott.