Comment Re: microsofties here is your chance to party (Score 1) 98
It's an oldschool attitude to not touch things
It's called engineering.
, from back in the day where software was so flaky that chances were someone had already 'exploited' the bug to do something non-malicious.
It drives me fucking crazy, having been born pretty much into the internet age where the corrected answer can be available in *seconds*.
Just because we are in the era of the Interweebz, that does not mean everything is a web app whose solutions can be put together in seconds. Specially something like a compiler, a shared library or an embedded system. You have to think of regression testing and crap like that, the backlog of issues that are begging fixing, etc, etc, etc. As a result, you do not touch things unless you truly need to, in a controlled manner.
If it is a web-based system with limited visibility, yeah, slap that fix and test it right there, just browse the page to see that it works. A web service or composite other systems depend on, hmmm, first device a functional test with SoapUI just to validate behavior before and after the change. An enterprise system with hundreds of developers and thousands of issues in back logs, slow down, time to prioritize a bit. Something system-level, and used by millions, hold on your danged horses.
I'm not saying the Glibc developers did the right thing at first - I mean, calling a bug "unexploitable" just like that, that is arrogance, not competence or prudence.
But that is a far cry from saying oh, we know what it is, we can put some code in place in seconds. Slapping some code changes =/= fix. A fix is a code change preceded by a cost analysis and followed by a regression/acceptance test, Internet or no Internet.
It's pretty obvious from the description what the bug is, so saying you aren't going to fix it is, as you say, pure laziness.
In this particular case, perhaps. In general, see my previous sentences above.