Interesting info about the Crowdstrike coding issue.
I commented on that post that there is a tool “valgrind” among others that is SOP for identifying such coding failures and potential vulnerabilities ... it appears incorporating such into the release pipeline is not part of Crowdstrike’s methodology or someone wanted this to go out. My gut tells me they needed to shut something down and if their driver is a component of the distributed computer network necessary to offload processing used in the rogue election tabulation processes ... that network just got shut down. In a professional model code that fails to incorporate basic code inspection and validation techniques is clearly flawed. TBD + WWG1WGA :)