We must remember always that accusation is not proof, and that conviction depends upon evidence and due process of law. We will not walk in fear - one, of another. We will not be driven by fear into an age of un-reason, if we dig deep in our history and our doctrine, and remember that we are not descended from fearful men; Not from men who feared to write, to speak, to associate, and to defend causes that were - for the moment - unpopular.
This is too rich! Microsoft's windowsupdate.microsoft.com site got exploited by the Code Red thingy. Sigh.... Wipe.... Oh man, that's just chuckle-worthy! Register's article
Nice posts mutt. I gotta pipe in here and say that these are EXACTLY the type of sloppy product and sploppy quality control and terrible security examples that we were debating in my last post about PHP and MS security stuff.
Its when products like the OPERATING SYSTEM and WEBSERVER are commonly and easily exploited that I scoff. And these are NOT always due to available patches that are not applied, or configuration, etc, they are due to plain ole holes that are unbeknownst to the user.
The fact that "updates.microsoft.com" got slammed by one of the exploits should be enough to convince ANYONE. The extra "resources" available to MS (per the aforementioned PHP and MS story and the security manager at MS himself) have proven time and time again to NOT be any advantage. These clowns consistently produce crappy products, there is no debate in that.
Want a solution to all the problems, checkout this [url=http://www.redhat.com]microsoft security update[/url]
Comments
Re: MS Site gets tagged by Code Red
HAHAHAHAHAHAHAHAHAHAHAHA!!!!!!!
Nice posts mutt. I gotta pipe in here and say that these are EXACTLY the type of sloppy product and sploppy quality control and terrible security examples that we were debating in my last post about PHP and MS security stuff.
Its when products like the OPERATING SYSTEM and WEBSERVER are commonly and easily exploited that I scoff. And these are NOT always due to available patches that are not applied, or configuration, etc, they are due to plain ole holes that are unbeknownst to the user.
The fact that "updates.microsoft.com" got slammed by one of the exploits should be enough to convince ANYONE. The extra "resources" available to MS (per the aforementioned PHP and MS story and the security manager at MS himself) have proven time and time again to NOT be any advantage. These clowns consistently produce crappy products, there is no debate in that.
Want a solution to all the problems, checkout this [url=http://www.redhat.com]microsoft security update[/url]