For the past 7 years Microsoft has released security patches for their products on the second Tuesday of each month. Following tradition, Microsoft just issued its largest security patch ever on October 12th, Patch Tuesday. Let me say again that this is the largest patch ever from Microsoft. A total of 49 vulnerabilities are fixed with 16 patches and this far exceeds the previous record of 34.
One of the most notorious exploits, that was mostly fixed, was the Stuxnet virus. This is the virus that attacked the Bushehr nuclear power plant in Iran earlier this year. I think it was a mistake when we coined the word “virus” to describe these attacks. We forget that what we call a virus is a direct attack by an individual or group. It’s almost as if we accept virus activity like we would accept having a cold. Make no mistake, this virus is not about a few stolen credit card numbers. There is a war going on. There are good guys and bad guys. The good guys are called “White Hat Hackers”, the bad guys are called “Black Hat Hackers”, and they are locked in mortal combat.
The introduction of the Stuxnet Virus changed the game. It amazed and horrified all the current experts. The attack on Bushehr was and still is, a big deal. The Stuxnet virus attacked a physical plant, and a nuclear plant at that. No longer a simple attack on software but a full blown attack on hard objects.
Please Note: Author is not responsible for damage to your computer from the use or misuse of the information contained in this article.
As you know, Windows XP has to be restored, from time-to-time, because, well… It blows. The update service at Microsoft adds stuff that seems to burden the system. If you install a program, it generally does not clean itself out of the registry. Shareware and freeware programs are especially sinister in this. And, of course, spyware and viruses are rampant.
But this time, it was not their fault. It was mine. I tried a development program on two computers and two got wrecked. I was able to continue using this one, so I did not worry too much about it.
Then came the day when I had to worry too much about it.
Continue reading “Error 432 and 101” »
