I was trying to just report the facts. The initial report by the google "expert" was claiming that it was a trivial coding error in an "unsafe" programming language. The "unsafe" part is just nonsense since that is the only language that drivers can be programmed in. The trivial coding error also turns out to be false.
I was trying to just report the facts. The initial report by the google "expert" was claiming that it was a trivial coding error in an "unsafe" programming language. The "unsafe" part is just nonsense since that is the only language that drivers can be programmed in. The trivial coding error also turns out to be false.
R.e. accidental or not: it's anyone's guess but I'm just telling you what happened. Also, again, this wasn't a "coding" error so much as a borked data file error.
R.e. Linux... the windows/linux debate is a theological discussion as much as anything with tech (or wanna be) tech people. Yes windows has had more than it's share of problems, but also, until recently it had something like 90% of the desktop market, so MUCH bigger attack surface. Again, not a windows fan-boy, just stating facts. Also, note that Linux has a similar "big brother" type system like this crowdstrike driver called eBPF. It is claimed that it can't crash the operating system, but it can definitely do similar things like intercept (and change) data returned by low level system calls. The Linux version though is completely wild west and programs can can be installed by anyone with administrative access, vs the microsoft version that requires a physical security dongle to digitally sign (i.e. verify the validity of) the driver.
I was trying to just report the facts. The initial report by the google "expert" was claiming that it was a trivial coding error in an "unsafe" programming language. The "unsafe" part is just nonsense since that is the only language that drivers can be programmed in. The trivial coding error also turns out to be false.
R.e. accidental or not: it's anyone's guess but I'm just telling you what happened. Also, again, this wasn't a "coding" error so much as a borked data file error.
R.e. Linux... the windows/linux debate is a theological discussion as much as anything with tech (or wanna be) tech people. Yes windows has had more than it's share of problems, but also, until recently it had something like 90% of the desktop market, so MUCH bigger attack surface. Again, not a windows fan-boy, just stating facts. Also, note that Linux has a similar "big brother" type system like this crowdstrike driver called eBPF. It is claimed that it can't crash the operating system, but it can definitely do similar things like intercept (and change) data returned by low level system calls. The Linux version though is completely wild west and programs can can be installed by anyone with administrative access, vs the microsoft version that requires a physical security dongle to digitally sign (i.e. verify the validity of) the driver.