by Mike Masnick
Mon, Jun 4th 2012 7:37pm
We've discussed in the past just how dangerous our reliance on Certificate Authorities "signing" security certificates has become. This is a key part of the way we handle security online, and yet it's clearly subject to abuse. The latest such example: the now infamous Flame malware that targeted computer systems in the Middle East was signed by a "rogue" Microsoft certificate -- one which was supposed to be used for allowing employees to log into a remote system. Microsoft rushed out a security update over the weekend, but that doesn't change the core problem: the whole setup of relying so heavily on secure certificates seems to be increasingly dangerous.
If you liked this post, you may also be interested in...
- New Malware Attack Tries To Trick People By Pretending To Be EFF
- AP Sues FBI Over Impersonating An AP Reporter With A Fake AP Story
- Leading DarkNet Market Agora Temporarily Suspends Service Over Tor Vulnerability Concerns
- Windows 10 Reserves The Right To Block Pirated Games And 'Unauthorized' Hardware
- Microsoft Launches Special 'Scott McNealy' Edition Of Windows