Microsoft Revokes Trust In 28 of Its Own Certificates
Trailrunner7 writes "In the wake of the Flame malware attack, which involved the use of a fraudulent Microsoft digital certificate, the software giant has reviewed its certificates, found nearly 30 that aren't as secure as the company would like, and revoked them. Microsoft also released its new updater for certificates as a critical update for Windows Vista and later versions as part of today's July Patch Tuesday. Microsoft has not said exactly what the now-untrusted certificates were used for, but company officials said there were a total of 28 certificates affected by the move. However, the company said it was confident none of them had been compromised or used maliciously. The move to revoke trust in these certificates is a direct result of the investigation into the Flame malware and how the attackers were able to forge a Microsoft certificate and then use it to impersonate a Windows Update server."
I'm hardly a Microsoft fan, but good! They seem to be taking a proactive approach here.
For large sets, this will be our guide even unto death, for the LORD will work for each type of data it is applied to...
OT, but related (somewhat):
> Verisign last year and now Microsoft plus SSL encryption being picked apart nothing is really safe on the web anymore.
Yes, nothing works because M$ doesn't work, then computers as a rule don't work, too. Do people still have some minimal grasp of logic? Or is this a feeble attempt at creating FUD?
BTW, am I supposed to buy a computer with a "secure boot" with keys from Verisign and M$?
Let me say that bluntly: enemies of the USA will manage to get keys (at what price, I can only wonder) the next day, while Linux users will have to purchase M$ (copyrighted?) keys to put Linux on their own PCs (maybe).
Again, secure boot is safe for who, really?
The purpose for secure boot is to protect the hardware from non-Windows operating systems. It's irony.
Help stamp out iliturcy.