|
Edited on Sun Apr-02-06 03:28 AM by RoyGBiv
It's not quite what I was getting at, though. Also, I'm not real clear on the point of your final comment. The latest flaw is a zero-day exploit, which basically means exploits are already implemented and being used. This is not the same as a situation involving a security expert finding a flaw and giving MS time to fix it before it becomes widely known. Zero-day exploits need to be reported immediately, regardless of the wishes of the programmers.
Anyway, what I was getting at ...
Some security people suggest MS is aware of a lot of the flaws in their various pieces of software even before the security experts are and are relying on the closed source to keep them secret, having no intention of touching them in anything approaching a timely manner unless someone else discovers it and it goes public. It's the same theory behind bean counters at other companies being aware of and not disclosing problems with their products until someone makes it an issue. Think car company that knows its cars will explode when hit a certain way in an accident. The cost of fixing it or admitting a problem is higher overall than the alternative of waiting, dealing with the PR fallout, and throwing out a fix at some later date, maybe. Some flaws in IE, for example, have been known by the public for a long time, and MS apparently has absolutely no intention of fixing them. They've already established no one can sue them successfully for these flaws, and as long as they have a strangelhold on the marketplace, the only real motivation to fix them at all comes from high volume/high income customers such as corporations that demand it and have the cash to make their demands seem appealing.
MS once relied on fairly regular releases of new versions of its OS and other software, which were sold rather than distributed as fixes, to make this manner of approaching quality control seem less obvious. "Oh, that was just a DOS 6.0 problem ... DOS 6.22 fixes it." "Oh, that was Windows 3.11 problem. Windows 95 changes everything," etc. But, after XP, MS essentially stopped delivering new product as it has delayed and delayed beyond reasonable expectations its newest release, meaning updates to correct these problems have not been forthcoming. Sure, they keep their regular patch cycle, which is absurdly controlled imo, but the patches generally address issues that have been problems for so long, the damage done to Average Consumer is already apparent in that they've either had their system compromised already or they've fallen into the game of beliving it's perfectly normal to have to pay other companies to protect them, without ever really fixing the problem itself, by using a partial, essentially temporary barrier between the flaw and those who would exploit it.
The issue has become one of time. Yes, with closed source, flaws are somewhat harder to detect, but given enough time, they will be detected and exploited by people who have nothing but destructive motives. The current version of IE has been around so long now that these more and more dangerous flaws, which have been present since the day it was released we should note, are being discovered by people who exploit the flaws rather than those who simply report them. What was discovered in this case was not a flaw in and of itself, but the fact that a flaw had already been discovered by others and was being used maliciously, a subtle but important distinction. If the source were open, which I realize won't happen, or if MS dedicated more of its resources to finding and fixing these flaws before they become problems, I and many others would cut them a lot more slack. But, they don't do that. They wait until a zero-day exploit is in the wild before assinging a team to correct it. Too little, too late.
I'm happier every day I have kicked the MS habit.
|