Is there not responsibility at some level as well to Microsoft for having a kernel which even loaded this? Not just because of the apparent corruption, but also ... it was, I heard.. signed and given a bit of an MS blessing.
This crap shouldn't be run in kernel space. But putting that aside, we need kernels that will be resilient to and reject this stuff.
This crap shouldn't be run in kernel space. But putting that aside, we need kernels that will be resilient to and reject this stuff.