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...
- The Internet Of Things Is a Security And Privacy Dumpster Fire And The Check Is About To Come Due
- Paris Court Says Search Engines Don't Need To Block Torrent Searches
- DOJ Pushes Out Legislation Proposal To Undercut Microsoft Case Decision About Overseas Searches
- Half Of TSA's 30,000 Employees Accused Of Misconduct; Nearly A Third Multiple Times
- Agent's Testimony Shows FBI Not All That Interested In Ensuring The Integrity Of Its Forensic Evidence