If Mac OS has a remote code exploit which affects every single installed Mac, you can bet I'll report it.
If I reported every time some vanishingly <1% percentage of the M$ install base had a problem (which is the scale of the bug you're talking about), I'd never be doing anything else.
That's not bias, that's picking the scale of reporting.
Seriously - remote code exploits have been known about for decades now, and how to ELIMINATE THEM COMPLETELY has been known about for decades. There actually is genuinely no excuse to have them in any code written by software engineers working for a large company, that can absolutely afford the resources to fix the problem.
It should take any competent toolsmith about a week to write a utility to identify *every single line of code* that might be a remote code exploit possibility. Give them a few months and they should be able to enhance the heuristics to suit the specific codebase, and even potentially make changes in a semi-automated fashion.
There is no excuse for not doing that. Really. None.
Re: Snow Leopard issue
Date: 2009-10-16 00:12 (UTC)If I reported every time some vanishingly <1% percentage of the M$ install base had a problem (which is the scale of the bug you're talking about), I'd never be doing anything else.
That's not bias, that's picking the scale of reporting.
Seriously - remote code exploits have been known about for decades now, and how to ELIMINATE THEM COMPLETELY has been known about for decades. There actually is genuinely no excuse to have them in any code written by software engineers working for a large company, that can absolutely afford the resources to fix the problem.
It should take any competent toolsmith about a week to write a utility to identify *every single line of code* that might be a remote code exploit possibility. Give them a few months and they should be able to enhance the heuristics to suit the specific codebase, and even potentially make changes in a semi-automated fashion.
There is no excuse for not doing that. Really. None.