2 ms·
Better that one vendor incompetently write a driver than have Microsoft open the floodgates with a shockingly insecure API 'feature' (again). It's much easier
by roc 17y ago
Better that one vendor incompetently write a driver than have Microsoft open the floodgates with a shockingly insecure API 'feature' (again).
It's much easier to replace third parties than the OS.
- tptacek 17y agoI think pretty much all the OS vendors have equally bad track records with kernel/userland interface design. But, having done a few device driver audits, I respectfully disagree, and submit to you that if your job exposed you to 3rd party driver code, you too would rather MSFT took a risk on kernel APIs than increase the number of drivers.
- roc 17y agoDon't get me wrong: I would absolutely prefer MSFT write a proper API to handle the necessary requests, rather than leave it to vendors to write drivers. But in reality no API will cover every corner case. And if the choice is between vendors writing drivers to cover those situations, or Microsoft leaving a 'hole' in the API which allows arbitrary instructions to be passed through, I'll take vendor drivers every time.